Home Creators Posts Import Register Favorites Logout

Content

If you are getting an Unauthorized error when pulling the Docker image, follow htis guide.

To pull the docker image, create a personal CLASSIC access token first here - make sure the read:packages permission is enabled: https://github.com/settings/tokens/new

And then you can run this command on your terminal:

docker logout ghcr.io

docker login ghcr.io -u username -p accesstoken

Now you can run:

docker pull ghcr.io/debridmediamanager/zurg:latest

Video to setup zurg on Windows: https://youtu.be/KnSipkn45lk

Comments

Departed69

I am trying to pull the docker container for the first time. Followed these instructions and when I run the docker pull command, I get Error response from daemon: denied. Any ideas how to troubleshoot this?

Adam

I'm still getting permission denied even though I subscribed.

JonnySiHi

echo (github personal access token) | docker login ghcr.io -u (github username) --password-stdin && docker pull ghcr.io/debridmediamanager/zurg:latest

Von

Issue: Unable to Pull Docker Image from GitHub Container Registry (GHCR) Context: I'm trying to pull a Docker image from GHCR using the following command: bash Copy code docker pull ghcr.io/debridmediamanager/zurg:latest Steps Taken: Generated a new classic GitHub token with read:packages and write:packages permissions. Used the token to log in to GHCR. Here are the logs showing the login process: bash Copy code root@server:~# docker logout ghcr.io Removing login credentials for ghcr.io bash Copy code root@server:~# echo "my_new_token" | docker login ghcr.io -u --password-stdin WARNING! Your password will be stored unencrypted in /root/.docker/config.json. Configure a credential helper to remove this warning. See https://docs.docker.com/engine/reference/commandline/login/#credential-stores Login Succeeded Attempted to pull the image, but received an error despite the successful login. bash Copy code root@server:~# docker pull ghcr.io/debridmediamanager/zurg:latest Error response from daemon: denied Additional Troubleshooting: Regenerated the token multiple times. Created entirely new tokens, deleting old ones to avoid conflicts. Verified each token was configured with read:packages permissions. Each token allowed successful login, but pulling the image continues to fail with a "denied" error. Request: If anyone has encountered a similar issue with GHCR or knows why access might be denied despite successful login, I’d appreciate any advice or solutions

HumanUFO

I was having a similar issue, turned out to be an issue with using pass as a docker credential store. I probably misconfigured it somehow. Anyways, I fixed it by removing the credsStore line from $HOME/.docker/config.json and running docker login ghcr.io again