Docker can't mount directory inside veracrypt container

[Fettpet]

Description

It seems that docker is unable to mount a directory inside a veracrypt volumn.

Steps to reproduce the issue:

1. Install Veracrypt
2. Create an encrypted file container. The volume is standard veracrypt volume. The Encryption is AES. The Hash Algorithm is SHA-512. I used 10GB size. I doesnt store large files inside the container
3. Mount the file. I used the T for the volum.
4. create the files T:\bar.txt and T:\test\foo.txt
5. Open a powershell
6. enter "docker run -v T::/project -w /project ubuntu:latest ls"

Describe the results you received: The command ls doesn't output anything.

Describe the results you expected: I expect that the directory test and the file bar.txt are outputed by the command ls. The above command works for other windows directories like C:\user\fettpet\test

Output of docker version:

Client: Cloud integration: v1.0.20 Version: 20.10.10 API version: 1.41 Go version: go1.16.9 Git commit: b485636 Built: Mon Oct 25 07:47:53 2021 OS/Arch: windows/amd64 Context: default Experimental: true

Server: Docker Engine - Community Engine: Version: 20.10.10 API version: 1.41 (minimum version 1.12) Go version: go1.16.9 Git commit: e2f740d Built: Mon Oct 25 07:41:30 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.11 GitCommit: 5b46e404f6b9f661a205e28d59c982d3634148f8 runc: Version: 1.0.2 GitCommit: v1.0.2-0-g52b36a2 docker-init: Version: 0.19.0 GitCommit: de40ad0

Output of docker info:

Client: Context: default Debug Mode: false Plugins: buildx: Build with BuildKit (Docker Inc., v0.6.3) compose: Docker Compose (Docker Inc., v2.1.1) scan: Docker Scan (Docker Inc., 0.9.0)

Server: Containers: 17 Running: 1 Paused: 0 Stopped: 16 Images: 15 Server Version: 20.10.10 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true 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: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: 5b46e404f6b9f661a205e28d59c982d3634148f8 runc version: v1.0.2-0-g52b36a2 init version: de40ad0 Security Options: seccomp Profile: default Kernel Version: 5.10.60.1-microsoft-standard-WSL2 Operating System: Docker Desktop OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 24.94GiB Name: docker-desktop ID: P3BB:3CDO:SMX2:KKBO:CK4S:IJNO:WEWD:HNON:2MV3:NA5K:S7PM:2D2Q Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 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

[Fettpet]

There is a workaround to mount inside a veracrype volumn. I test it in windows

1. mount the veracrypt container
2. use task manager to stop all docker related tasks
3. start docker
4. now you can mount a volumn inside the veracrypt container.