search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 289 forks source link

lost everything; containers, images and volumes following update to 4.34.3 #14355

Open oues81 opened 1 week ago

oues81 commented 1 week ago

Description

I cant find my data after update to 4.34.3 I had a lot of containers, images and volumes Cannot find the issue Using docker with wsl2 linux containers Tried to install 2 old version 4.34.2 and 4.33.1 Nothing in AppData\Local\Docker\wsl\data or in /mnt/wsl/docker-desktop-data/data/docker

Reproduce

Update from inside docker Docker opening with no data at all

Expected behavior

Successfull update without issue and existing data availlable.

docker version

Client: Version: master-dockerproject-2022-03-26 API version: 1.42 Go version: go1.17.8 Git commit: dd7397342a Built: Sun Mar 27 00:09:40 2022 OS/Arch: windows/amd64 Context: desktop-linux Experimental: true

Server: Docker Desktop 4.33.1 (161083) Engine: Version: 27.1.1 API version: 1.46 (minimum version 1.24) Go version: go1.21.12 Git commit: cc13f95 Built: Tue Jul 23 19:57:19 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.7.19 GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc: Version: 1.7.19 GitCommit: v1.1.13-0-g58aa920 docker-init: Version: 0.19.0 GitCommit: de40ad0

docker info

Client: Context: desktop-linux Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc., v0.16.1-desktop.1) compose: Docker Compose (Docker Inc., v2.29.1-desktop.1) debug: Get a shell into any image or container (Docker Inc., 0.0.34) desktop: Docker Desktop commands (Alpha) (Docker Inc., v0.0.14) dev: Docker Dev Environments (Docker Inc., v0.1.2) extension: Manages Docker extensions (Docker Inc., v0.2.25) feedback: Provide feedback, right in your terminal! (Docker Inc., v1.0.5) init: Creates Docker-related starter files for your project (Docker Inc., v1.3.0) sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0) scout: Docker Scout (Docker Inc., v1.11.0)

Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 27.1.1 Storage Driver: overlayfs driver-type: io.containerd.snapshotter.v1 Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc version: v1.1.13-0-g58aa920 init version: de40ad0 Security Options: seccomp Profile: unconfined Kernel Version: 5.15.153.1-microsoft-standard-WSL2 Operating System: Docker Desktop OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 5.792GiB Name: docker-desktop ID: 9812d918-7e6a-48d3-a523-13dba47cb115 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 Registry: https://index.docker.io/v1/ Labels: com.docker.desktop.address=npipe://\.\pipe\docker_cli Experimental: false Insecure Registries: hubproxy.docker.internal:5555 127.0.0.0/8 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support WARNING: No blkio throttle.write_bps_device support WARNING: No blkio throttle.read_iops_device support WARNING: No blkio throttle.write_iops_device support WARNING: daemon is not using the default seccomp profile

Diagnostics ID

Diagnostics ID: DC8C352E-1AF1-4C9B-B04D-1294773CAF29/20241009175212

Additional Info

I can provide logs needed

bsousaa commented 4 days ago

have you enabled the containerd image store? (Settings > General > use containerd for pulling and storing images)

oues81 commented 2 days ago

have you enabled the containerd image store? (Settings > General > use containerd for pulling and storing images)

Containerd not enabled.

I finally realized that the docker data .VHDX was completely reset and therefore I lost everything permanently. I tried to check the free space on the disk to find something, but my time is limited.

I still don't know what happened but it strictly followed the Docker update. While trying to troubleshoot I uninstalled and reinstalled Docker and I think it does resets the vhdx....

Conclusion, backup the vhdx to avoid a similar situation.