Hi,
I lost access after the last docker-desktop update to the data. I moved the docker-desktop-data to another Drive by using wsl --unregister and wsl --import. After the last update I noticed docker desktop is no longer using my docker-desktop-data from drive D: but actually created a new docker-desktop-data.
I tried to unregister it, but import the tar file, I still have from a few days ago, but it seems not be recognized by docker desktop. I can access the distribution using \wsl$ so I see that the volumes, containers/images are all there, but I can’t access/use them anymore with docker desktop…
Is there something like a upgrade docker-desktop-data I can apply?
any hints? Any logs I should/can look into?
To be honest, I am pretty p… by this “application” at the moment!
I can confirm that after downgrading to Docker v.4.30.0 I can access my old containers again… Thx Misty Moore for contacting me and providng that hint… Anyhow not sure what’s going on there… 4.31.0 is IMHO a broken/faulty update!
I also do not fully understand why I was connected privately from a high school person. Is docker recently working with high school students?
rimelek
June 25, 2024, 9:03am
4
There was an issue when containers and images disappeared after the upgrade
opened 03:55PM - 06 Jun 24 UTC
closed 04:10PM - 10 Jun 24 UTC
status/acknowledged
area/WSL2
version/4.30.0
version/4.31.0
version/4.31.1
### Description
After launching the latest upgrade, there are no containers, … images and volumes visible in the UI.
Also nothing visible, if I execute:
docker ps -a
docker image ls -a
docker volume ls
I see that the volume folders are still there under: \\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes
Can anybody recommend a solution?
### Reproduce
1. install the latest update (version 4.31.0)
2. launch Docker for Windows (launches automatically)
3. use the menu in the UI to open Containers, Volumes etc
4. also check using Docker command line tools
### Expected behavior
Upgrade successful and Docker for Windows starts up and previous volumes, images and containers are visible / usable.
### docker version
```bash
docker version
Client:
Version: 26.1.4
API version: 1.45
Go version: go1.21.11
Git commit: 5650f9b
Built: Wed Jun 5 11:29:54 2024
OS/Arch: windows/amd64
Context: desktop-linux
Server: Docker Desktop 4.31.0 (153195)
Engine:
Version: 26.1.4
API version: 1.45 (minimum version 1.24)
Go version: go1.21.11
Git commit: de5c9cf
Built: Wed Jun 5 11:29:22 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.33
GitCommit: d2d58213f83a351ca8f528a95fbd145f5654e957
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
```
### docker info
```bash
docker info
Client:
Version: 26.1.4
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.14.1-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.27.1-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.32
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.24
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: C:\Program Files\Docker\cli-plugins\docker-feedback.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.2.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.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.9.3
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 4
Server Version: 26.1.4
Storage Driver: overlay2
Backing Filesystem: tmpfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
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: d2d58213f83a351ca8f528a95fbd145f5654e957
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.146.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 6
Total Memory: 9.717GiB
Name: docker-desktop
ID: 04323cfe-2afb-408d-84f8-942d3b89e298
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
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
6117E11F-C8D4-414E-9ED5-1D0AE0C8A0AE/20240606155414
### Additional Info
_No response_
it was fixed in Docker Desktop 4.31.1
but If I understand you correctly, your problem is different, because you moved your data distribution to a different storage and the new version does not recognize it. I don’t use DD on Windows actively, so I don’t know any solution, but you can also report it on GitHub.