[BUG] Failed remounting volumes on restart of my pc

[remco-pc]

Description

Error response from daemon: error while mounting volume '/var/lib/docker/volumes/vps2_domain/_data': failed to mount local volume: mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Debian/7f0790219a3c6f23307f66ac618d4d0423238bb93e626c4b498af7e0c67b00b9:/var/lib/docker/volumes/vps2_domain/_data, flags: 0x1000: no such file or directory Error response from daemon: Container 943c3983f0ca8675caa0f6c750cc7aaa8b20fa540af99fdf0ad62d82768e56d1 is not running

In my docker compose file, i started to use volumes. this because the copy of the main volume became very large (multiple GB) my Desktop pc could not get it running, so i switched to use multiple volumes. Which becomes handy because i can re-use them between docker instances.

i then remove all docker volumes first (not the data) with docker volume rm ...

and after that rebuild the image again and it will stay up to the next reboot. this is on windows docker desktop (Docker version 24.0.7, build afdd53b)

So there are 2 bugs, 1: big application copy on debian desktop is failing (hangs (gave up after several hours)) 2: docker volumes cannot be mounted after reboot on windows

Steps To Reproduce

No response

Compose Version

Docker Compose version v2.23.3-desktop.2
Docker Compose version v2.23.3-desktop.2

Docker Environment

Client: Docker Engine - Community
 Version:    24.0.7
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.0-desktop.2
    Path:     /usr/local/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.23.3-desktop.2
    Path:     /usr/local/lib/docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.21
    Path:     /usr/local/lib/docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  0.1
    Path:     /usr/local/lib/docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.10
    Path:     /usr/local/lib/docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.2.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-scout

Server:
 Containers: 8
  Running: 5
  Paused: 0
  Stopped: 3
 Images: 44
 Server Version: 24.0.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  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 logentries splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f
 runc version: v1.1.10-0-g18a0cb0
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.133.1-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 15.52GiB
 Name: docker-desktop
 ID: 584b0fbc-106f-48bc-a855-24c51d8a6cd4
 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
 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

Anything else?

the memory size is only 16 GB in docker info, while i have 32 GB

[ndeloof]

seems to me this is a Docker Desktop (or maybe WSL2) issue, unrelated to Docker Compose. Can you please try to reproduce using plain docker volume create ... and docker run -v ... commands commands ?

[remco-pc]

then i think it is a docker desktop bug, where can i place the issue or can you handle it ?

I only use docker-compose and have no idea of the underlying technology. we will be a month further if i know how to do that i can use my team better. The reason for this is: i really need to delete the created volume and this is only possible to delete the image / container as well. the mount itself stays correct.

[NZnick]

i think it is a docker desktop bug, where can i place the issue or can you handle it ?

If you need to report a bug in Docker Desktop for Windows you can log one here https://github.com/docker/for-win. Best to read the README and search existing issues first.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[1EDExg0ffyXfTEqdIUAYNZGnCeajIxMWd2vaQeP]

bump

[stale[bot]]

This issue has been automatically marked as not stale anymore due to the recent activity.