moby: 1.12rc2: Cannot create containers with overlay network.

Output of docker version:

~$ docker version
Client:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   906eacd
 Built:        Fri Jun 17 20:45:29 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   906eacd
 Built:        Fri Jun 17 20:45:29 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.0-rc2
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge host null
Swarm: active
 NodeID: dajmc033h7dlq7ckrb3lrvs73
 IsManager: Yes
 Managers: 1
 Nodes: 1
 CACertHash: sha256:a66134e21db54aece05e342480dddf6eebcf7f369399daa79558c5bc32affe81
Runtimes: default
Default Runtime: default
Security Options: seccomp
Kernel Version: 4.4.13-boot2docker
Operating System: Boot2Docker 1.12.0-rc2 (TCL 7.1); HEAD : 52952ef - Fri Jun 17 21:01:09 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: default
ID: YROR:XV6G:I5E5:JZCH:ED37:I36J:TQA4:GWOE:VCQM:KBSX:CB44:L6YG
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 37
 Goroutines: 112
 System Time: 2016-06-23T14:31:01.553076833Z
 EventsListeners: 1
Username: sdemura
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Insecure Registries:
 127.0.0.0/8

Additional environment details (AWS, VirtualBox, physical, etc.):

Docker Toolbox 1.12rc2 for Mac.

Steps to reproduce the issue:

Launch docker vm
Initialize a swarm
Create an overlay network
Attempt to run a container with new network

$ docker swarm init --listen-addr 192.168.99.100:2377
Swarm initialized: current node (dajmc033h7dlq7ckrb3lrvs73) is now a manager.
~$ docker network create test_network -d overlay
e4n63vh4t0z8142kp2j0jbsiq
~$ docker run --net test_network hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
a9d36faac0fe: Pull complete
Digest: sha256:e52be8ffeeb1f374f440893189cd32f44cb166650e7ab185fa7735b7dc48d619
Status: Downloaded newer image for hello-world:latest
docker: Error response from daemon: network test_network not found.
See 'docker run --help'.
~$ docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
8625ea168e65        bridge              bridge              local
3a9b6494bc4a        docker_gwbridge     bridge              local
189fe6f3aa0e        host                host                local
dlursqan326x        ingress             overlay             swarm
2a9e2cefe947        none                null                local
e4n63vh4t0z8        test_network        overlay             swarm

Describe the results you received: I was not able to create a container with the overlay network I created.

Describe the results you expected: I would expect to be able to run a container with the overlay network I created.

Additional information you deem important (e.g. issue happens only occasionally): This is consistently reproducible.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 18 (8 by maintainers)

Most upvoted comments

@sdemura @IevgenKabanets @kelseyhightower regarding the original intent of this issue (supporting docker run to accept network managed by swarm), we are actively working on supporting that functionality. Lets use this issue to track that functionality.

+19

mavenugo on Jul 8, 2016

@cpuguy83 perfect. I think many would appreciate to have this limitations in documents somehow. Would definitely be less issues created. For all I know, there will be a big amount of ppl, that will assume this functionality present.

EugeneK6S on Jun 24, 2016

@mrjana – I hope these limitations will be noted in the documentation, but I do hope this will change in future updates.

@levgenKabanets – I have the same sentiments.

I was very much under the impression I wouldn’t have to deal with a 3rd party K/V store, which would have vastly simplified my (automated) infrastructure.

sdemura on Jun 23, 2016

What I see is whenever you create user defined overlay on the master node, it is not reflected on the worker node. But when you try creating services and then assigning the task or scaling it out, the overlay network gets automatically created and now it shows up on the worker nodes.

ajeetraina on Jul 4, 2016

Closing as fixed.

mrjana on Sep 14, 2016