-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No such image" when running in docker container on Unrair #2241
Comments
Hi @MomoMiles i did not know Unraid. Perhaps ask the question directly to the Unraid Glances plugin maintainer: https://forums.unraid.net/profile/70671-atribe/ |
same issue here, but think this is not unraid related. If I try to create the docker direct from the command line using docker run -d --restart="always" -p 61208-61209:61208-61209 -e GLANCES_OPT="-w" -v /var/run/docker.sock:/var/run/docker.sock:ro --name "Glances"--pid host nicolargo/glances:latest i get docker: Error response from daemon: pull access denied for host, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. I did try logging in with my docker credentials from the command line, didnt seem to resolve. According to my research this is due to one of the repos being set as private. |
@nicolargo its not doing anything fancy. This is the docker run command it uses:
|
Related to #2233 |
@nicolargo I saw that. Issue is that I have reinstalled multiple times on host, bridge, and my custom network. Same error everytime. |
What is the version of the Glances image used ? |
I have tried Latest and Latest-Alpine I believe |
Unsure if related, but I’ve been getting the following from my watchtower notification for the past 6hrs: Could not do a head request for "nicolargo/glances:latest-full", falling back to regular pull. |
I too get the same watchtower notification on multiple servers. Only started happening a day ago. It still seems to be able to later pull and recreate the container after it "falls back to regular pull" I assume.. curious though on the initially failed head request only happening recently. |
Same issue here... following... |
FYI, I've disabled the LABEL env to stop the monitoring on the glances container for the moment, this will stop the alerts at least. |
Same error for me from Watchtower. Edit: Just to add, this is with Docker on a Ubuntu VM. |
Same here. |
Same issue here.
|
Same here: level=warning msg="Reason: registry responded to head request with "404 Not Found", auth: "not present"" container=/glances image="nicolargo/glances:latest-full" |
I am not using unraid and I get this error in watchtower. This seems to affect other docker images as well: containrrr/watchtower#1528 |
Same here, no unraid here, purely docker with a watchtower monitoring the containers. |
If you all try it with this tag then it should work: Found this fix on the Unraid forums. Not sure why anything else doesn't work. |
Confirmed working with new tag. Thanks
|
Just chiming in. Watchtower user without unraid use here: same error. Other containers seem to have updated to avoid the cause of the issue. Not sure this applies here but for the sake of spreading the information: |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Describe the bug
I am running into an issue where everytime I setup a fresh docker container with glances on unraid, it gives me a python error
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Launches properly
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: