Hello Docker Community,
I am encountering a very persistent and frustrating issue with Docker Desktop on my Windows machine, and I’m hoping someone can offer some insight or a solution.
Issue Type: Core Docker functionality (image pulling/authentication) failure.
OS Version/Build:
- Operating System: Windows 11
- OS Build: 22631.5624
App Version:
- Docker Desktop Version: Docker Engine v28.3.2
Problem Description:
I am consistently unable to pull Docker images from Docker Hub, specifically n8n/n8n (though I suspect it would affect any public image). The command docker pull n8n/n8n consistently returns the error Error response from daemon: pull access denied for n8n/n8n, repository does not exist or may require ‘docker login’.
The critical and perplexing part of this issue is that my docker login command consistently reports Login Succeeded immediately before the docker pull attempt.
Steps to Reproduce (and detailed troubleshooting already attempted):
- Open Command Prompt/PowerShell as Administrator.
- Run docker login:
- C:\Windows\System32>docker login
- Authenticating with existing credentials… [Username: xxx]
- i Info → To login with a different account, run ‘docker logout’ followed by ‘docker login’
- Login Succeeded
(Note: I’ve also tried docker login -u xxx and the web-based login flow, all reporting Login Succeeded.)
- Immediately run docker pull n8n/n8n in the same session:
- C:\Windows\System32>docker pull n8n/n8n
- Using default tag: latest
- Error response from daemon: pull access denied for n8n/n8n, repository does not exist or may require ‘docker login’
Troubleshooting Steps Already Attempted (and their outcomes):
- Complete Reinstallation of Docker Desktop: I have performed a full clean uninstall and reinstall of Docker Desktop. This involved:
- Stopping and removing the old Docker container (docker stop, docker rm).
- Crucially, removing the old Docker data volume (docker volume rm YOUR_N8N_DATA_PATH after confirming its name via docker volume ls).
- Uninstalling Docker Desktop via Windows Apps & Features.
- Manually cleaning up residual Docker files/folders in AppData, Program Files, etc.
- Downloading and installing the latest Docker Desktop installer.
- Restarting the laptop after installation.
- Despite this, the pull access denied error persists on a fresh install.
- Windows System File Checks:
- Ran sfc /scannow from an Administrator Command Prompt, which reported: Windows Resource Protection found corrupt files and successfully repaired them.
- Ran DISM /Online /Cleanup-Image /RestoreHealth from an Administrator Command Prompt, which reported: The restore operation completed successfully. The operation completed successfully.
- Restarted the laptop after both commands.
- Ensured Docker Desktop is Running: Confirmed the Docker whale icon is active in the system tray before attempting docker pull.
- Running Commands as Administrator: All docker commands have been executed from a Command Prompt opened “Run as administrator.”
- Docker Desktop Updates: I am running the latest version of Docker Desktop, and I have installed any new updates prompted by the app.
Additional Context: I’ve also experienced general instability with Docker Desktop itself, occasionally requiring a full laptop shutdown to get it to open and run correctly after being closed or a system restart.
My Questions:
- What could be causing this specific behavior where docker login succeeds but docker pull immediately fails with “access denied”?
- Are there any deeper diagnostic steps, cache clearances, or configuration checks within Docker Desktop or Windows that I might be missing?
- Could there be a specific network, proxy, or security software (firewall/antivirus) interaction that is blocking the pull despite successful authentication? (I have not yet tried temporarily disabling these, but can if advised).
Any help or guidance would be greatly appreciated as I’m completely blocked from using Docker. Thank you in advance!