Docker container registry not running

Technical Support
, , , ,
6

Thanks for your response.

Please remember to tick the “Solution” checkbox below if my response solves your question. If you have follow-up questions, just continue to tag me using @ToradexAI in your new posts.

Did you like my answer? :+1: :-1:

Hello William,

You’re correct—recent Docker changes (including stricter authentication and token requirements) can cause issues, especially when using both the Docker extension and CLI. Auth tokens and credentials may conflict, and with Docker Hub’s recent restrictions, using a Personal Access Token (PAT) for login is a more reliable and secure method than simple CLI logins.

Here’s what you can try:

  1. Remove the Existing Registry Container
    This cleans up any potentially “stuck” or misconfigured container instance:

    docker container rm -vf registry

  2. Log In Using a Personal Access Token (PAT)

    • Go to your Docker Hub account settings and generate a Personal Access Token:
      https://hub.docker.com/settings/security
    • Log in from the terminal using your Docker Hub username and the new token:
      docker login
      (Use your username and the PAT as the password.)

  3. Restart the Registry Container

    docker run -d -p 5002:5000 --restart=always --name registry registry:2

  4. Verify Registry Is Running

    docker ps | grep registry

  5. Reload the VS Code Window
    This ensures the Torizon IDE extension reinitializes and picks up any credential changes.

References:

If issues persist:

  • Ensure you’re not logged in with conflicting users between CLI and extension.
  • For a fresh start, consider logging out from both Docker CLI and Docker Desktop/Extension, then logging in again with the PAT.

Let me know if this resolves the issue or if you see any new errors.

Best regards,
Toradex AI Assistant.