Crash when DD attempts renaming daemon.json and windows-daemon.json
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- docker
- Ambito
- desktop
Direzione di ricerca
Start by investigating Docker Desktop's Windows settings update path, especially the rename operations for daemon.json and windows-daemon.json described in the crash message. Check how the Hyper-V configuration handles those files and whether another process can keep them locked; use the provided reproduction steps and diagnostics ID to narrow it down. Done means Docker Desktop no longer crashes when these settings files cannot be renamed.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Bug report
Bug description
This occurs every time I leave Docker Desktop running overnight. Docker Desktop attempts to rename daemon.json and windows-daemon.json. These actions fail with "Access is denied", which causes Docker Desktop to crash.
Reproduction steps
- Disable WSL
- Have IT install Docker Desktop 4.93.0 using the Hyper-V option instead of WSL
- Have IT add your account to the local "docker-users" group
- Restart PC
- Start Docker Desktop.
- Run one or more containers (not sure yet if this is required)
- Leave Docker Desktop running overnight.
- Wake up to a crashed application with the given error.
Error message copied from one of the crashes:
updating settings: rename C:\Users\oginri.docker\daemon.json.tmp-2109403358 C:\Users\oginri.docker\daemon.json: The process cannot access the file because it is being used by another process.
rename C:\Users\oginri.docker\windows-daemon.json.tmp-393510585 C:\Users\oginri.docker\windows-daemon.json: The process cannot access the file because it is being used by another process.
Seemed very similar to ticket 193.
Platform
Windows
Version information
Client:
Version: 29.8.1
API version: 1.56
Go version: go1.26.8
Git commit: 4a63305
Built: Tue Sep 15 16:28:39 2026
OS/Arch: windows/amd64
Context: desktop-linux
Server: Docker Desktop 4.93.0 (240920)
Engine:
Version: 29.8.1
API version: 1.56 (minimum version 1.40)
Go version: go1.26.8
Git commit: 464cd50
Built: Tue Sep 15 16:25:38 2026
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.3.5
GitCommit: 1294c24a7da8e5a793ed378161673abe94118892
runc:
Version: 1.5.1
GitCommit: v1.5.1-0-g8f2685a4
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Client:
Version: 29.8.1
Context: desktop-linux
Debug Mode: false
Plugins:
agent: Docker AI Agent Runner (Docker Inc.)
Version: v1.141.0
Path: C:\Program Files\Docker\cli-plugins\docker-agent.exe
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.31.0
Path: C:\Program Files\Docker\cli-plugins\docker-ai.exe
buildx: Docker Buildx (Docker Inc.)
Version: v0.37.1
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v5.5.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.47
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Docker Inc.)
Version: v0.4.4
Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe
dhi: CLI for managing Docker Hardened Images (Docker Inc.)
Version: v0.0.7
Path: C:\Program Files\Docker\cli-plugins\docker-dhi.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.31
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: v0.43.3
Path: C:\Program Files\Docker\cli-plugins\docker-mcp.exe
model: Docker Model Runner (Docker Inc.)
Version: v1.2.6
Path: C:\Program Files\Docker\cli-plugins\docker-model.exe
offload: Docker Offload (Docker Inc.)
Version: v0.6.33
Path: C:\Program Files\Docker\cli-plugins\docker-offload.exe
pass: Docker Pass Secrets Manager Plugin (beta) (Docker Inc.)
Version: v0.2.2
Path: C:\Program Files\Docker\cli-plugins\docker-pass.exe
sandbox: "docker sandbox" is deprecated, use Docker Sandboxes instead (Docker Inc.)
Version: v0.13.0
Path: C:\Program Files\Docker\cli-plugins\docker-sandbox.exe
scout: Docker Scout (Docker Inc.)
Version: v1.24.0
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 7
Running: 1
Paused: 0
Stopped: 6
Images: 22
Server Version: 29.8.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Discovered Devices:
cdi: docker.com/gpu=webgpu
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 1294c24a7da8e5a793ed378161673abe94118892
runc version: v1.5.1-0-g8f2685a4
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 7.0.14-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 15.61GiB
Name: docker-desktop
ID: 6cdd789b-9732-4072-bf77-d6113040660e
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=npipe://\\.\pipe\docker_cli
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
::1/128
127.0.0.0/8
Live Restore Enabled: false
Firewall Backend: iptables
Diagnostics ID
538B2EB6-B53E-45F5-8273-19011199E218/20261115224203
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 53
- Fork
- 24
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di docker/desktop-feedback
-
Codex sandbox template seeds MCP gateway config with keys Codex does not recognize (type, headers)Apertaplatform/macos
Difficoltà 1/5 1-3 ore Idoneità per principianti 82/100
docker/desktop-feedback#721 ·
-
Location: /home/linuxbrewApertakind/enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
docker/desktop-feedback#259 ·
-
kind/bug platform/windows
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
docker/desktop-feedback#862 ·
-
kind/bug platform/windows
Difficoltà 5/5 Più di una settimana Idoneità per principianti 45/100
docker/desktop-feedback#861 ·
-
kind/bug platform/macos
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
docker/desktop-feedback#860 ·
Tutte le issue di docker/desktop-feedback
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
milind-soni/OpenMausBot#6495 ·
I maintainer di solito rispondono entro 1 giorno
-
bug triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
telegramdesktop/tdesktop#31653 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement ui/ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
jbigler/railswitch#243 ·
I maintainer di solito rispondono entro 1 giorno
-
技能库不能筛选仅可更新的Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
xingkongliang/skills-manager#678 ·
I maintainer di solito rispondono entro 1 giorno