for-win
for-win copied to clipboard
docker
Docker Desktop "Refreshing container files..." forever
Description
Instead of saying that the container is stopped, it seems like it's trying to access its files forever, saying "Refreshing container files..."
Reproduce
- Create container in Docker Desktop.
- Make sure it's stopped.
- Go to "Files" tab.
Expected behavior
Some comprehensive message saying that the container is stopped.
docker version
Docker Desktop 4.28.0 (139021)
Docker EngiClient:
Cloud integration: v1.0.35+desktop.11
Version: 25.0.3
API version: 1.44
Go version: go1.21.6
Git commit: 4debf41
Built: Tue Feb 6 21:13:00 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Desktop
Engine:
Version: 25.0.3
API version: 1.44 (minimum version 1.24)
Go version: go1.21.6
Git commit: f417435
Built: Tue Feb 6 21:14:25 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0ne
v25.0.3
docker info
Client:
Version: 25.0.3
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.12.1-desktop.4
Path: /usr/local/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.24.6-desktop.1
Path: /usr/local/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container. (Docker Inc.)
Version: 0.0.24
Path: /usr/local/lib/docker/cli-plugins/docker-debug
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /usr/local/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.22
Path: /usr/local/lib/docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: /usr/local/lib/docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.0.1
Path: /usr/local/lib/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: /usr/local/lib/docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.5.0
Path: /usr/local/lib/docker/cli-plugins/docker-scout
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-scan: no such file or directory
Server:
Containers: 22
Running: 4
Paused: 0
Stopped: 18
Images: 65
Server Version: 25.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: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.146.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 7.637GiB
Name: docker-desktop
ID: 44e76403-0c80-483c-9f4c-164ace199f46
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
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
1A8B7A3C-92E8-40CC-8D2A-E723D974B0C5/20240408052411
Additional Info
No response
I haven't heard anyone here mention a fix to it yet. If this issue still persists maybe try to do it on the docker cli until it gets fixed.
same windows 11 22631.3593 and WSL2 Docker Desktop 4.30.0 (149282) I am kind of a novice, so when the container is stopped you can't view files? Well my container exits on error, and its erroring out because I need to edit a config. So how can I edit that config if the container is exiting itself? :s
I have added a 9GB file because I need it to restore a DB in a MSSQL image, but updating the container files seems to take forever
if I try to open the folder where I have put the new file from the files tab, it does not open and the "expand" arrow just revets back to the horizontl position
Docker desktop v4.30.0
Same here. I can see the files when the container is running but I cannot when it is stopped. Maybe it has something to do with that ?
Same here. Windows 10. Also have sign-in issue describe here: https://github.com/docker/for-mac/issues/7160
Same here. I can see the files when the container is running but I cannot when it is stopped. Maybe it has something to do with that ?
Actually this seems to be the case for me as well. Though this guy does it in the course at 23:25 just fine: https://www.youtube.com/watch?v=GFgJkfScVNU
Same here. I can see the files when the container is running but I cannot when it is stopped. Maybe it has something to do with that ?
Actually this seems to be the case for me as well. Though this guy does it in the course at 23:25 just fine: https://www.youtube.com/watch?v=GFgJkfScVNU
@DavesClassyCode I'm using Windows 11. Are you perhaps using Windows as well? The guy in the video seems to have Linux or Mac. If that's the case, maybe this problem is isolated for Windows host machines only
Same here. I can see the files when the container is running but I cannot when it is stopped. Maybe it has something to do with that ?
Actually this seems to be the case for me as well. Though this guy does it in the course at 23:25 just fine: https://www.youtube.com/watch?v=GFgJkfScVNU
@DavesClassyCode I'm using Windows 11. Are you perhaps using Windows as well? The guy in the video seems to have Linux or Mac. If that's the case, maybe this problem is isolated for Windows host machines only
Yes, I'm running Windows 10.
Windows for me too. I have renounced to use Docker because of this bug.
I'm using Windows 11. Are you perhaps using Windows as well? The guy in the video seems to have Linux or Mac. If that's the case, maybe this problem is isolated for Windows host machines only
@GTziolas I can confirm that it happens on MacOS, so I don't believe this problem is isolated to Windows hosts.
I have this issue on Win 10.
I updated a file and made a typo, so the container wouldn't start. Now it's either "refreshing" or cyclically restarting.
Thank you, chatGPT: docker cp "C:\Users\server\Desktop\New folder\data\patcher.py" patcher-1.1.3:/app/patcher.py
