You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Start-Service docker (config/daemon.json has bridge:none)
docker network ls (Look for nat network - renamed by design as we only support one in WS2016)
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
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:
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
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
Windows Client (Version 1607 - OS Build 14393.576)
The text was updated successfully, but these errors were encountered: