Skip to content

Files not updating inside container after updating from 4.29.0 to 4.30.0 #14060

Closed
Closed
Files not updating inside container after updating from 4.29.0 to 4.30.0#14060
Labels
area/hyper-varea/mountskind/bugstatus/acknowledgedstatus/needs-investigatingversion/4.30.0

Description

@8ctopus
8ctopus
opened on May 9, 2024

Description

I have a Windows setup for development using the Hyper-V engine instead of WSL2 for inotify to work.

When a file is updated in the Windows file system, it's not automatically updated inside the container since 4.30.0. (The file is in the same state as when the container was started.)

Reverting to 4.29.0 fixed the problem.

Reproduce

  • start a container with shared folder
  • edit in windows a file in the shared folder
  • the file is not changed in the container

Expected behavior

When a file is changed in the windows filesystem, it should get updated inside the container.

docker version

Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.1.1
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        4cf5afa
 Built:             Tue Apr 30 11:48:43 2024
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.30.0 (149282)
 Engine:
  Version:          26.1.1
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.9
  Git commit:       ac2de55
  Built:            Tue Apr 30 11:48:28 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.31
  GitCommit:        e377cd56a71523140ca6ae87e30244719194a521
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    26.1.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.29
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.23
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.8.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 2
  Running: 2
  Paused: 0
  Stopped: 0
 Images: 2
 Server Version: 26.1.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
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e377cd56a71523140ca6ae87e30244719194a521
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.6.26-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 1.92GiB
 Name: docker-desktop
 ID: 561f1203-4318-48df-ad63-6796ec8c0eca
 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=npipe://\\.\pipe\docker_cli
 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

5FC51C8F-9C92-4D9D-910E-CC14DB38403E/20240509120112

Additional Info

Very similar to this older issue: #5530

Activity

  1. Image8ctopus
    added
    needs-triage
    on May 9, 2024
  2. Imagedocker-robot
    added
    version/4.30.0
    on May 9, 2024

  3. fikusz01 commented on May 9, 2024

    @fikusz01
    fikusz01
    on May 9, 2024

    Same problem here. Just upgraded to v4.30.0

  4. AngelCifuentes commented on May 9, 2024

    @AngelCifuentes
    AngelCifuentes
    on May 9, 2024

    Same issue here in multiple configs (Windows 10/11, Mac docker client).
    Folder appear Mounted and with privileges but, when make changes in host, aply it in swap file tmp, not real file, not sync.

    I'll rollback to 4.29.0 and all ok. Try with more configs, caché flush, other volumes, images, etc and add ":consistent" tag to volume, nothing work, only rollback to 4.29.0.

    To rollback:
    Download 4.29 for your OS from link
    https://docs.docker.com/desktop/release-notes/#4290

    Open terminal:
    .\ Docker_installer_4_29_0_path.exe install --disable-version-check

  5. pneme commented on May 10, 2024

    @pneme
    pneme
    on May 10, 2024

    Same problem.

  6. Image8ctopus
    changed the title [-]File not updating inside container after updating from 4.29.0 to 4.30.0[/-] [+]Files not updating inside container after updating from 4.29.0 to 4.30.0[/+] on May 10, 2024
  7. Imagemilas
    added
    area/mounts
    kind/bug
    area/hyper-v
    status/acknowledged
    status/needs-investigating
    and removed
    needs-triage
    on May 10, 2024

  8. berkanumutlu commented on May 11, 2024

    @berkanumutlu
    berkanumutlu
    on May 11, 2024

    I have same problem. I rebuild containers, start older containers(already builded and using containers before Docker v4.30.0) and later tried that comment #5530 (comment) in this older issue: #5530 but not worked. So I had to downgrade Docker version to v4.29.0 for temporary solution. #13207 (comment)

  9. nirvana72 commented on May 11, 2024

    @nirvana72
    nirvana72
    on May 11, 2024

    same problem, and how to roll back to 429 safely? uninstall 430 will lost my container

  10. berkanumutlu commented on May 11, 2024

    @berkanumutlu
    berkanumutlu
    on May 11, 2024

    same problem, and how to roll back to 429 safely? uninstall 430 will lost my container

    I didn't uninstall Docker, just downloaded v4.29.0 from this link and tried running the installer with from the CLI <installer_file_path>/DockerInstaller.exe install --disable-version-check and I didn't lose the containers.

  11. 34 remaining items

  12. isntw commented on May 26, 2024

    @isntw
    isntw
    on May 26, 2024

    Same problem here, it's so frustrating

  13. ctberdon commented on May 27, 2024

    @ctberdon
    ctberdon
    on May 27, 2024

    any updates if this will be fixed?

  14. pdeberranger commented on May 28, 2024

    @pdeberranger
    pdeberranger
    on May 28, 2024

    Same for me, downgrade is the only issue!

  15. w-A-L-L-e commented on May 28, 2024

    @w-A-L-L-e
    w-A-L-L-e
    on May 28, 2024

    Same problem on macos sonoma with 4.2.30. Downgrade to 4.2.29 fixes that issue but has different issue that containers go to sleep and don't wake up if inactive for a while.
    When this happens you can't stop/start the containers either you also have to restart entire docker app:

    (HTTP code 500) server error - cannot stop container: ebac4d9da09c28734cb46d21e30cd301ed5d04dff5410314d9ff36922475ceac: tried to kill container, but did not receive an exit event

  16. 8ctopus commented on May 28, 2024

    @8ctopus
    8ctopus
    on May 28, 2024
    Author

    @w-A-L-L-e Same issue on Windows. If I go for lunch and put the computer to sleep, when I turn it back on, the docker containers are no longer working. Have to restart docker desktop and the containers.

  17. Myke79 commented on May 28, 2024

    @Myke79
    Myke79
    on May 28, 2024

    That's another issue described here:
    docker/desktop-feedback#113

    And that one is still unsolved since 4.26.0.
    The only solution to downgrade to 4.25.2 and not upgrading, until the linked issue and this one is solved.

  18. josepdecid commented on May 31, 2024

    @josepdecid
    josepdecid
    on May 31, 2024

    I faced the same problem when updating to 4.30.0. Rolling back to 4.29.0 fixes the problem.
    On Mac, just download the 4.29.0 release and replace the current installation.

  19. Webinx commented on Jun 1, 2024

    @Webinx
    Webinx
    on Jun 1, 2024

    Any ETA on fixing the issue? Prior versions are also affected by very annoying issues that were fixed in version 4.30. This should have the highest priority.

  20. RichardForshaw commented on Jun 3, 2024

    @RichardForshaw
    RichardForshaw
    on Jun 3, 2024

    Upgraded recently and also finding the same issue. Surprised it is a month old. Watching for fix.

  21. MihaelaStoica commented on Jun 3, 2024

    @MihaelaStoica
    MihaelaStoica
    on Jun 3, 2024

    Thank you all for your patience on this and apologies again for the issue. We will include a fix in Docker Desktop 4.31 which is due to be released this week.

  22. hahatulk commented on Jun 6, 2024

    @hahatulk
    hahatulk
    on Jun 6, 2024

    Same problem here

  23. x0rsw1tch commented on Jun 7, 2024

    @x0rsw1tch
    x0rsw1tch
    on Jun 7, 2024

    🤞 Hope that this fixes #13894, been stuck on 4.25.2 for a while now

  24. AngelCifuentes commented on Jun 10, 2024

    @AngelCifuentes
    AngelCifuentes
    on Jun 10, 2024

    With this patch (4.31.0) solved the file updating problem #14060 but not docker/desktop-feedback#113 , needed to close and open docker cli again to work

    Tested in:

    • Windows 10 / 11 laptops (Dell, Hp, etc)
    • Hyper V

    Last versión that this work ok is 4.25.2

  25. maxcleme commented on Jun 10, 2024

    @maxcleme
    maxcleme
    on Jun 10, 2024
    Member

    Closing this issue because a fix has been released in Docker Desktop 4.31.0. See the release notes for more details.

  26. Imagemaxcleme
    closed this as completedon Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/hyper-varea/mountskind/bugstatus/acknowledgedstatus/needs-investigatingversion/4.30.0

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions