Issues using file explorer from Docker Desktop

[tsybot]

Description

In Docker desktop, when working in the Files tab, folders stop opening and close immediately after opening

Reproduce

1. First we pull any container with Linux, for example: docker pull php:8.4.0alpha2-apache-bullseye
2. The next we run it container. docker run -it --name php_test_container --privileged -p 7789:80 php:8.4.0alpha2-apache-bullseye
3. Go to "Files" tab of this container
   
4. Now check /usr/ folder and all work
   
5. For get bug you need modify php.ini file, so go open in file editor /usr/local/etc/php/php.ini-production
   
6. im change 'display_errors = Off' to 'display_errors = On' and save file /usr/local/etc/php/php.ini-production
   
7. Now you must NOT CLOSE HIDE EDITOR and go to Exec tab
   
8. Now back to Files tab and try to open /usr folder and its dead, open and immediately close
   

Video demonstration
(not my video)

Expected behavior

Not dead Files tab

docker version

docker version
Client:
 Version:           27.0.3
 API version:       1.46
 Go version:        go1.21.11
 Git commit:        7d4bcd8
 Built:             Sat Jun 29 00:03:32 2024
 OS/Arch:           windows/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.32.0 (157355)
 Engine:
  Version:          27.0.3
  API version:      1.46 (minimum version 1.24)
  Go version:       go1.21.11
  Git commit:       662f78c
  Built:            Sat Jun 29 00:02:50 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.18
  GitCommit:        ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
 runc:
  Version:          1.7.18
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

docker info
Client:
 Version:    27.0.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.15.1-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.28.1-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.32
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.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.25
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.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.10.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 23
  Running: 19
  Paused: 0
  Stopped: 4
 Images: 25
 Server Version: 27.0.3
 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: 1
 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: ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.153.1-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 24
 Total Memory: 54.91GiB
 Name: docker-desktop
 ID: 193a45c3-763a-49fe-8aae-e8b074e9ab47
 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: 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
WARNING: daemon is not using the default seccomp profile

Diagnostics ID

C5249FDB-749E-49C6-BA31-1EFA366DFC60/20240720031501

Additional Info

No response

[umut-saribiyik88]

I have the same issue, and a possible workaround is to focus on the folder that's not expanding and then press the spacebar on your keyboard to open it.

This issue is also happening on mac:

docker/for-mac#7229

[tsybot]

I have the same issue, and a possible workaround is to focus on the folder that's not expanding and then press the spacebar on your keyboard to open it.

Yes, it seems it can help with folders located at the root of the file system like /etc /usr and so on. But what should I do when I need to open the /usr/local/etc/php/php.ini-production file? Yes, I focus on /usr and press the space bar and open /usr, but how do I continue to focus on /usr/local? Clicking on the arrows or the mouse on local will close the /usr folder

[tsybot]

I came up with a temporary bypass bug that will allow you to not stop working until the docker team fixes the problem, but it’s a little long, you need to make a shared folder “Volumes” for example C:\sharefolder:/var/www/test and now you can copy the necessary files to change into this folder and edit the file on Windows and then copy it back. For example:
cp /usr/local/etc/php/php.ini-production /var/www/test/php.ini-production
Now you modify php.ini-production on windows in C:\sharefolder\php.ini-production
cp /var/www/test/php.ini-production /usr/local/etc/php/php.ini-production

[ianef]

I have the same issue too. The /opt folder in my case get changed by apps running when my container starts. I can't open the folder via mouse or keyboard actions. It briefly displays the sub folders and immediately closes the sub items again. Oddly other changed folders seem to be OK, I can't think why /opt would be unique.

A workaround is to right click and choose Save. This allows you to make a current copy to some other local location. However this is pretty tedious and needs to be done every time you want to inspect changes.

[ibaraki-douji]

Like the others users i also have the issue.

For me it happen sometimes to some folder, i don't see a pattern on the folder names but for me it only affect MODIFIED elements and only one folder at the time (so if my /var is bugged the others don't bug)

A other workaround that i manage to do but does not work 100% of the time is to click once on the bugged folder, switch tabs (from Files to Exec for example) and then go back. It sometimes work with only one click, sometimes two and sometimes it just don't work ...

[alp1396]

Same here. Issue seen only for folders that are MODIFIED

[Chrisp186]

I have the same issue... but I seem to have it if I add a file and don't close all the folders and restart that container, I then can't open that folder but can open others.

[lannotimo]

Same issue. Reported on the Forums on Apr 18 and still not fixed.

[m33ts4k0z]

Same issue guys. This is so frustrating 😒

[rensrongen]

It was reported here a while ago already: #14112

It's frustrating because it makes the file browser unusable in many cases.

[landism]

Docker Desktop 4.34.0 will contain a fix for this issue.

[tsybot]

Docker Desktop 4.34.0 contains a fix for this issue.

Where you find this information?

[ianef]

Excellent, many thanks for this. When will this be released?

[aurelijus-kj]

Facing the same issue after installing Docker Desktop (Version: 4.32.0) on MacOS (Ventura 13.6.6). Cannot access the /usr and /opt directories marked as modified in the Files tab.

Also, completely restarting the container (deleting and then re-creating it again) seems to solve the issue temporarily, modified directories can be accessed. But after some time the directories become inaccessible again.

[bsousaa]

@ianef Docker Desktop 4.34 is currently planned for August 29th.

[lorenrh]

4.34.0 has been released with a fix for this issue, more information o the release notes.

I'll be closing this issue, but if the problem persists please open a fresh issue!