The default-created network disappears on Windows after OS restart #12927
Description
Description
When using Windows-based containers, sometimes I cannot start my compose project after the OS restart. The following error is displayed:
time="2025-05-10T22:11:32+02:00" level=warning msg="a network with name local_default exists but was not created by compose.\nSet
external: trueto use an existing network"
network local_default was found but has incorrect label com.docker.compose.network set to "" (expected: "default")
Steps To Reproduce
- Switch to windows containers.
- Create a basic compose project without explicitly defined
networks. - Restart Windows machine.
- Starting containers is not possible because of the error.
Compose Version
Docker Compose version v2.36.2-desktop.1
Docker Environment
Client:
Version: 28.2.2
Context: desktop-windows
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.4.0
Path: C:\Program Files\Docker\cli-plugins\docker-ai.exe
buildx: Docker Buildx (Docker Inc.)
Version: v0.24.0-desktop.2
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
cloud: Docker Cloud (Docker Inc.)
Version: v0.3.9
Path: C:\Program Files\Docker\cli-plugins\docker-cloud.exe
compose: Docker Compose (Docker Inc.)
Version: v2.36.2-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.41
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Docker Inc.)
Version: v0.1.9
Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.29
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
mcp: Docker MCP Plugin (Docker Inc.)
Version: dev
Path: C:\Program Files\Docker\cli-plugins\docker-mcp.exe
model: Docker Model Runner (Docker Inc.)
Version: v0.1.24
Path: C:\Program Files\Docker\cli-plugins\docker-model.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scout: Docker Scout (Docker Inc.)
Version: v1.18.1
Path: C:\Users\domsew\.docker\cli-plugins\docker-scout.exe
WARNING: Plugin "C:\\Users\\domsew\\.docker\\cli-plugins\\docker-feedback.exe" is not valid: failed to fetch metadata: fork/exec C:\Users\domsew\.docker\cli-plugins\docker-feedback.exe: The system cannot find the file specified.
Server:
Containers: 12
Running: 0
Paused: 0
Stopped: 12
Images: 533
Server Version: 28.2.2
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics internal l2bridge l2tunnel nat null overlay private transparent
Log: awslogs etwlogs fluentd gcplogs gelf json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 22631 (22621.1.amd64fre.ni_release.220506-1250)
Operating System: Microsoft Windows Version 23H2 (OS Build 22631.5335)
OSType: windows
Architecture: x86_64
CPUs: 16
Total Memory: 31.73GiB
Name: domsew
ID: ed08e4d5-d204-48c9-8b75-2d3cdf494f6e
Docker Root Dir: C:\ProgramData\Docker
Debug Mode: false
Labels:
com.docker.desktop.address=npipe://\\.\pipe\docker_cli
Experimental: false
Insecure Registries:
::1/128
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
Anything else?
The problem does not occur when I use Linux-based containers. I can't figure out when exactly the problem happens. It is probably after a computer restart, but I am not sure if it happens each time.