Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot connect container to user-defined NAT network on Windows #30102

Closed
JMesser81 opened this issue Jan 12, 2017 · 0 comments · Fixed by #30117
Closed

Cannot connect container to user-defined NAT network on Windows #30102

JMesser81 opened this issue Jan 12, 2017 · 0 comments · Fixed by #30117

Comments

@JMesser81
Copy link


BUG REPORT INFORMATION

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->

Description
I am running Docker v1.13.0-rc4 on my Windows 10 client. I specified “bridge”:”none” in the daemon/config.json file and then launched Docker daemon. I then created a user-defined NAT network successfully named mynat. I successfully launched a nanoserver container which was connected to the mynat network.

I then restarted the docker daemon and noticed that the user-defined nat network is renamed to “nat” – I believe this is by design.

However, I can no longer create a container which is connected to this nat network. Ipconfig is blank.

This has repro’d twice now on my system. Any ideas?

Steps to reproduce the issue:

  1. Start-Service docker (config/daemon.json has bridge:none)
  2. docker network create -d nat --subnet 172.16.0.0/16 --gateway=172.16.0.1 mynat
  3. Restart-Service docker
  4. docker network ls (Look for nat network - renamed by design as we only support one in WS2016)
  5. docker run -it --net=nat nanoserver cmd.exe (and other variants including specifying port mapping, not specifying network name, etc.)

Describe the results you received:
No IP Configuration present in the container

Describe the results you expected:
IP Configuration should be present in the container

Additional information you deem important (e.g. issue happens only occasionally):
Has repro'd multiple times

Output of docker version:

Client:
 Version:      1.13.0-rc4
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   88862e7
 Built:        Sat Dec 17 01:34:17 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.0-rc4
 API version:  1.25 (minimum version 1.24)
 Go version:   go1.7.3
 Git commit:   88862e7
 Built:        Sat Dec 17 01:34:17 2016
 OS/Arch:      windows/amd64
 Experimental: false

Output of docker info:

Containers: 3
 Running: 0
 Paused: 0
 Stopped: 3
Images: 40
Server Version: 1.13.0-rc4
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: l2bridge l2tunnel nat null overlay transparent
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 14393 (14393.576.amd64fre.rs1_release_inmarket.161208-2252)
Operating System: Windows 10 Enterprise
OSType: windows
Architecture: x86_64
CPUs: 12
Total Memory: 15.93 GiB
Name: jmesser-dev01
ID: BTUT:DTRE:DVUE:CIX6:CLFW:GJX4:GGV7:GWLQ:WHQQ:OUW5:ZL65:PGMP
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Windows Client (Version 1607 - OS Build 14393.576)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants