Description
Creating a custom Docker network succeeds on Windows Server 2019 but it is gone after rebooting the machine.
Steps to reproduce the issue:
- Log in to a clean Windows Server 2019.
- Add Containers feature and restart the OS.
- Install Docker (using the standard installation instructions at https://docs.docker.com/install/windows/docker-ee/)
- Restart the OS.
- Execute the following command in an elevated PowerShell console:
docker network create --driver nat --gateway 172.31.250.254 --subnet 172.31.250.0/24 mycustomnetwork
- Restart the OS.
- Execute
docker network ls.
Describe the results you received:
The previously created network is not listed.
Describe the results you expected:
The previously created network listed.
Additional information you deem important (e.g. issue happens only occasionally):
Happens all the time. Of course if there are containers started that use that network (when it still exists), the containers fail to start after reboot, because of the missing network. In that sense I would say it should be a high priority defect to get fixed.
Output of docker version:
Client: Docker Engine - Enterprise
Version: 18.09.5
API version: 1.39
Go version: go1.10.8
Git commit: be4553c277
Built: 04/11/2019 06:44:52
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Enterprise
Engine:
Version: 18.09.5
API version: 1.39 (minimum version 1.24)
Go version: go1.10.8
Git commit: be4553c277
Built: 04/11/2019 06:43:04
OS/Arch: windows/amd64
Experimental: false
Output of docker info:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 18.09.5
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows Server 2019 Datacenter Version 1809 (OS Build 17763.437)
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 8GiB
Name: sdfgsdgwin2019
ID: 4675:AROZ:6SG7:EFA6:5MCG:FD2B:LP5R:3V3Y:TD5K:XUST:EEUR:JOPT
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.):
VM in Azure.
Description
Creating a custom Docker network succeeds on Windows Server 2019 but it is gone after rebooting the machine.
Steps to reproduce the issue:
docker network create --driver nat --gateway 172.31.250.254 --subnet 172.31.250.0/24 mycustomnetworkdocker network ls.Describe the results you received:
The previously created network is not listed.
Describe the results you expected:
The previously created network listed.
Additional information you deem important (e.g. issue happens only occasionally):
Happens all the time. Of course if there are containers started that use that network (when it still exists), the containers fail to start after reboot, because of the missing network. In that sense I would say it should be a high priority defect to get fixed.
Output of
docker version:Output of
docker info:Additional environment details (AWS, VirtualBox, physical, etc.):
VM in Azure.