However, if I use either “osxfs (Legacy)” or “gRPC FUSE”, the size is reported to containers correctly, albeit with dramatically reduced performance.
Reproduce
Bind mount a large (>1TB) volume to a container in MacOS using VirtioFS and observe total size reported to container. It will not be correct.
Do the same using osxfs (Legacy) or gRPC FUSE and reported size will be correct.
Expected behavior
Bind mounting a large (>1TB) volume to a container in MacOS using VirtioFS should report correct total size.
docker version
Client:
Version: 27.2.0
API version: 1.47
Go version: go1.21.13
Git commit: 3ab4256
Built: Tue Aug 27 14:14:45 2024
OS/Arch: darwin/amd64
Context: desktop-linux
Server: Docker Desktop 4.34.2 (167172)
Engine:
Version: 27.2.0
API version: 1.47 (minimum version 1.24)
Go version: go1.21.13
Git commit: 3ab5c7d
Built: Tue Aug 27 14:15:15 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.20
GitCommit: 8fc6bcff51318944179630522a095cc9dbf9f353
runc:
Version: 1.1.13
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Description
When I select the default VirtioFS file sharing implementation in Docker settings, my 6TB bind mount only reports a total size of ~480GB to containers. Basically identical to this issue: https://forums.docker.com/t/macos-docker-bind-mount-reports-incorrect-free-space/137982
However, if I use either “osxfs (Legacy)” or “gRPC FUSE”, the size is reported to containers correctly, albeit with dramatically reduced performance.
Reproduce
Bind mount a large (>1TB) volume to a container in MacOS using VirtioFS and observe total size reported to container. It will not be correct. Do the same using osxfs (Legacy) or gRPC FUSE and reported size will be correct.
Expected behavior
Bind mounting a large (>1TB) volume to a container in MacOS using VirtioFS should report correct total size.
docker version
docker info
Diagnostics ID
0FE4C648-8DE7-4B20-BEA3-18D1D4648FEF/20241005213903
Additional Info
No response