docker-networking

来源： https://stackoverflow.com/questions/63446467/docker-share-network-with-windows-and-linux-containers

问题 Assuming we need to do this very rarely only at certain stages of development (to smoke test a few api calls), what is the simplest possible way to let a dockerized web service in project Bar access a dockerized web service in Project Foo? On a development Mac, Docker Engine: 18.09.2, Compose: 1.23.2, we have Project Foo and Project Bar which each have their own docker-compose files, each with a web service and a database service. Normally they run stand-alone, and are developed independently

问题 Assuming we need to do this very rarely only at certain stages of development (to smoke test a few api calls), what is the simplest possible way to let a dockerized web service in project Bar access a dockerized web service in Project Foo? On a development Mac, Docker Engine: 18.09.2, Compose: 1.23.2, we have Project Foo and Project Bar which each have their own docker-compose files, each with a web service and a database service. Normally they run stand-alone, and are developed independently

问题 Assuming we need to do this very rarely only at certain stages of development (to smoke test a few api calls), what is the simplest possible way to let a dockerized web service in project Bar access a dockerized web service in Project Foo? On a development Mac, Docker Engine: 18.09.2, Compose: 1.23.2, we have Project Foo and Project Bar which each have their own docker-compose files, each with a web service and a database service. Normally they run stand-alone, and are developed independently

问题 In our development environment, we manage 20+ containers with docker-compose files, but from time to time one of them acquires one IP from our network and we lost connectivity. When that happens, we manually shut down the container and the network. Is there a way to configure docker to avoid that specific IP address or subnet when we add more containers? Our docker version is: Client: Docker Engine - Community Version: 19.03.12 API version: 1.40 Go version: go1.13.10 Git commit: 48a66213fe

问题 I have Windows 10 Docker for Windows V. 1.12.5 Rev. 9503, which does not rely on boot2docker or VirtualBox anymore. I have a number of JBoss instances running in Docker images (172.18.0.2 is a database): instance 1: name: jboss-eap, IP: 172.18.0.3 instance 2: name: jboss-eap-arquillian, IP: 172.18.0.4 that shall be running at the same time. Each JBoss instance exports e.g. its 8787, 8080 and 8443 ports. I have also created a bridged network: docker network create --driver bridge --subnet 172

问题 So, here is what I am trying to achieve: A Jupyterhub server Which when accessed and you are not logged in, takes you to another web server (custom coded in Django) That web server uses OAuth to authenticate a user And a notebook container is spawned. This notebook container must be pre-populated with a token that is used by a custom library baked into the notebook Docker image to authenticate against a service. The notebook container needs to be able to communicate with the web server for

问题 So, here is what I am trying to achieve: A Jupyterhub server Which when accessed and you are not logged in, takes you to another web server (custom coded in Django) That web server uses OAuth to authenticate a user And a notebook container is spawned. This notebook container must be pre-populated with a token that is used by a custom library baked into the notebook Docker image to authenticate against a service. The notebook container needs to be able to communicate with the web server for

问题 I have an existing app that comprises of 4 docker containers running on the same host. They have been linked together using the link command. However, after some upgrades of docker, the link behaviour has been deprecated, and changed it seems. We are having issues where containers are loosing the link to each other now. So, docker says to use the new Network feature over link ed containers. But I can't see how this works. If 2 containers are in the same network, are the same ENV vars

问题 I need a service within a Docker Swarm stack which has one additional interface based on a macvlan network. This is cause the JBoss Cluster in this service needs to communicate via IP multicast, which is currently not supported in overlay networks. I have created the macvlan network like that: # Worker 1: docker network create --config-only --subnet 10.140.0.0/16 -o parent=ens224.800 --ip-range 10.140.1.0/24 swarm-multicast-config-only # Worker 2: docker network create --config-only --subnet