lema Posted October 14, 2022 Share Posted October 14, 2022 Hi all, So, I have this issue that after installing two docker containers successfully, I cannot install anything else anymore. I always run into the same error no matter what image I choose. As a background info, I needed to do controlled shutdown today from the menu because electrician cut the power for few minutes. After powering up, the docker service would not start and I figured to remove the docker img. That worked and I managed to get docker running. Installed PiHole & HomeAssistant, all good. Then tried to install mongodb and nothing worked anymore. Later removed HA and now I cannot install even it anymore. Here's the error I'm getting: Unable to find image 'ghcr.io/home-assistant/home-assistant:latest' locally docker: Error response from daemon: Head "https://ghcr.io/v2/home-assistant/home-assistant/manifests/latest": Get "https://ghcr.io/token?scope=repository%3Ahome-assistant%2Fhome-assistant%3Apull&service=ghcr.io": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See 'docker run --help'. Any suggestions? bifrost-diagnostics-20221014-2140.zip Quote Link to comment
JorgeB Posted October 15, 2022 Share Posted October 15, 2022 Check filesystem on disk1. Quote Link to comment
lema Posted October 16, 2022 Author Share Posted October 16, 2022 On 10/15/2022 at 11:09 AM, JorgeB said: Check filesystem on disk1. Tried this but did not solve the issue. I figured it might be some weird connectivity problem caused by PiHole. Stopped the PiHole container and tried to install HA again, but no luck. I tried few other times and actually managed it to start the download (see screenshot), but the process still fails at the end. Ones I even got the container visible in docker management but trying to start it caused an error. Overall the whole process seems weirdly slow. Quote Link to comment
Solution Kilrah Posted October 16, 2022 Solution Share Posted October 16, 2022 Make sure your DNS/network on unraid are NOT set to use something like PiHole running on unraid itself. Quote Link to comment
lema Posted October 17, 2022 Author Share Posted October 17, 2022 9 hours ago, Kilrah said: Make sure your DNS/network on unraid are NOT set to use something like PiHole running on unraid itself. This configuration has been working for ages. But did as you suggested and switched unRAID to use an other DNS and things started to work. Weird, but at least it works. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.