Ihar Hancharenka 5dff80e88e first
2023-03-27 16:52:17 +03:00

35 строки
1.6 KiB
Plaintext

docker inspect xd-admin -f "{{json .NetworkSettings.Networks }}"
https://forums.docker.com/t/error-only-one-instance-of-host-network-is-allowed/52280/4
network_mode: host
https://docs.docker.com/config/containers/container-networking/#dns-services
https://docs.docker.com/network/bridge/
"dns": ["10.20.1.2","10.20.1.3"]
https://docs.docker.com/compose/compose-file/#dns
https://docs.docker.com/compose/compose-file/#networks-top-level-element
https://medium.com/@kinghuang/docker-compose-anchors-aliases-extensions-a1e4105d70bd
https://github.com/docker/compose/issues/5621
Yes, they can't be used across different files.
! use extends
https://docs.docker.com/compose/compose-file/#extends
⠿ Network stafnet Error 0.0s
failed to create network stafnet: Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network
failed to create network: Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network
https://stackoverflow.com/questions/43720339/docker-error-could-not-find-an-available-non-overlapping-ipv4-address-pool-am/56136591#56136591
I ran in this problem with OpenVPN working as well and I've found a solution where you should NOT stop/start OpenVPN server.
Idea that You should specify what exactly subnet you want to use. In docker-compose.yml write:
networks:
default:
driver: bridge
ipam:
config:
- subnet: 172.16.57.0/24