The changes to the file on a host system are not visible from the inside container.

[EugenKon]

Description

This is the same as: docker/for-win#5530 but for Ubuntu 24.04

Changes to a mounted file into container are not visible.

More details:
hashicorp/nomad#23691 (comment)

Reproduce

I mounted file into container
Do some changes to the file on a host system
docker exec into container
less to the mounted file

Expected behavior

I expect to see the changed I did to the file on a host system. But they are not visible

docker version

Client: Docker Engine - Community
 Version:           27.1.1
 API version:       1.46
 Go version:        go1.21.12
 Git commit:        6312585
 Built:             Tue Jul 23 19:57:14 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          27.1.1
  API version:      1.46 (minimum version 1.24)
  Go version:       go1.21.12
  Git commit:       cc13f95
  Built:            Tue Jul 23 19:57:14 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.19
  GitCommit:        2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
 runc:
  Version:          1.7.19
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client: Docker Engine - Community
 Version:    27.1.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 6
  Running: 6
  Paused: 0
  Stopped: 0
 Images: 6
 Server Version: 27.1.1
 Storage Driver: btrfs
  Btrfs:
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 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: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.8.0-1012-aws
 Operating System: Ubuntu 24.04 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 15.42GiB
 Name: ip-172-31-0-179
 ID: b081ce08-a016-421c-aedc-85e8c7acd1ed
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  0.0.0.0/0
  127.0.0.0/8
 Live Restore Enabled: false

Diagnostics ID

bash: /opt/docker-desktop/bin/com.docker.diagnose: No such file or directory

Additional Info

This is Ubuntu 24.04

uname -a
Linux ip-172-31-0-179 6.8.0-1012-aws #13-Ubuntu SMP Mon Jul 15 13:40:27 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

[zagumaar]

I have the same issue on Ubuntu 22.04. it seems very similar to docker/for-win#14060 which was fixed in 4.31.0

The solution I found for now is to rollback to 4.29.0

[EugenKon]

@zagumaar There is not such version on Ubuntu 24.04 ) The earliest version is 26.0.0 =(

[zagumaar]

@EugenKon I found it here: https://docs.docker.com/desktop/release-notes/#4290

[furyozo]

@zagumaar's solution worked.

If you're using Windows and encounter an error message indicating that you can't upgrade Docker for Desktop because a higher version is already installed, you can bypass this by:

1. Downloading the version provided by @zagumaar.
2. Renaming it to DockerInstaller.exe.
3. Running the following CLI command: ./DockerInstaller.exe install --disable-version-check.

[rhessus]

Same problem since upgrading from 4.32 to latest releases. I'm on Pop!_OS 22.04.