You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docker pull progress stays at "Pulling fs layer" while data continues downloading #754
When pulling a large image, the terminal output remains at “Pulling fs layer” for several minutes, even though the corresponding temporary files in the containerd content store continue growing.
Expected behavior
The terminal should show download progress reflecting the actual transfer, followed by extraction and completion status.
Steps observed
Use Docker Desktop on Windows with the WSL2 backend and containerd image store.
Run docker pull deepmi/fastsurfer:cu132-v2.6.0 in PowerShell.
Interrupt the download with Ctrl+C while some layers are still downloading.
Run the same pull command again.
Observe that the output remains at “Pulling fs layer”, while the temporary download files continue growing.
Evidence
For one layer, the temporary file grew from 829,423,616 bytes at 00:23:51 to 861,929,472 bytes at 00:24:53 on October 18, 2026 (UTC+08:00), while the terminal progress did not update.
The behavior was also observed after restarting Docker Desktop.
An HTTP system proxy was enabled. Proxy modes and nodes were changed during troubleshooting. I have not determined whether the proxy is required to reproduce this behavior.
The underlying cause has not been identified.
The additional window in the screenshot is a custom read-only monitoring tool created with OpenAI Codex. It displays the amount of download data saved on disk and the estimated write rate, allowing progress to be observed independently of Docker’s terminal output. From this context I can see that the downloading isn't actually stopped while the powershell only shows "Pulling fs layer" during the whole process.
Finally it was downloaded successfully, so based on further observation, this appears to be a progress display issue rather than an actual download stall.
One additional observation: this issue seems to occur only when retrying an image pull that was interrupted partway through. I have now started pulling a different image (FreeSurfer) for the first time, and its progress is displaying normally.
Activity
Ryuta-dyc commentedon Oct 17, 2026
Ryuta-dyc commentedon Oct 17, 2026
One additional observation: this issue seems to occur only when retrying an image pull that was interrupted partway through. I have now started pulling a different image (FreeSurfer) for the first time, and its progress is displaying normally.