Directory stat inside bind mount doesn't update after host's changes

Open WilliamVenner opened this issue 9 months ago • 1 comments

Description

When the host adds a file or deletes a file from a directory inside a bind mount, the mtime and atime inside the container does not update.

Seems to happen with both Docker VMM and Apple Virtualization framework. I am using VirtioFS.

Reproduce

rm -rf /tmp/foo/bar/baz
mkdir -p /tmp/foo/bar/baz
touch /tmp/foo/bar/baz/file1.txt
stat /tmp/foo/bar/baz
docker run -d -it --rm --name docker-for-mac-stat-issue -v /tmp/foo:/home/container/foo ubuntu bash
docker exec docker-for-mac-stat-issue stat /home/container/foo/bar/baz
echo Sleeping for 5 seconds...
sleep 5
touch /tmp/foo/bar/baz/file2.txt
stat /tmp/foo/bar/baz
echo Sleeping for 5 seconds...
sleep 5
docker exec docker-for-mac-stat-issue stat /home/container/foo/bar/baz
docker container rm --force docker-for-mac-stat-issue
rm -rf /tmp/foo/bar/baz

Expected behavior

The mtime and atime should update accordingly.

docker version

Client:
 Version:           27.5.1
 API version:       1.47
 Go version:        go1.22.11
 Git commit:        9f9e405
 Built:             Wed Jan 22 13:37:19 2025
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.38.0 (181591)
 Engine:
  Version:          27.5.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.11
  Git commit:       4c9b3b0
  Built:            Wed Jan 22 13:41:25 2025
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.25
  GitCommit:        bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e946
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    27.5.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.7.3
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.20.1-desktop.2
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.32.4-desktop.1
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.38
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.4
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     /Users/venner-prism/.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:     /Users/venner-prism/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.16.1
    Path:     /Users/venner-prism/.docker/cli-plugins/docker-scout

Server:
 Containers: 17
  Running: 4
  Paused: 0
  Stopped: 13
 Images: 591
 Server Version: 27.5.1
 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: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc version: v1.1.12-0-g51d5e946
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.12.5-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 12
 Total Memory: 27.36GiB
 Name: docker-desktop
 ID: 0abf9a44-79bd-4065-912d-48ec044edd83
 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=unix:///Users/venner-prism/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

Diagnostics ID

8567437A-ADE3-4823-8DB5-940D8B4A4ED6/20250310123029

Additional Info

Navigating to the directory in Finder appears to propagate the updated stat to the container.

Mar 10 '25 12:03 WilliamVenner

Not sure if this is a different issue or related: when a container has accessed a file in a bind mount (persistent volume in K8s), it doesn't see any updated to this file on host side. I have to restart the container (K8s pod) to make the container see any file change. 🤔 wondering if the trick to navigate to the directory via Finder has the same effect as container restart?

Mar 10 '25 13:03 bschuhmann