Is anyone else having issues updating to 0.5.1? My install gets stuck at “Pulling new containers” then times-out and goes back to the settings page (still at 0.5.0). Once that fails over selecting “Install” again from the settings page simply errors out and requires a node restart for the install option to try and work again.
Update1: The 1st issue I’ve found is that DNS is hardcoded in the update so that it will always try to resolve at 8.8.8.8. If you run a private DNS (Pi-Hole, etc) you’ll need to punch a hole in your FW to allow Google DNS at 8.8.8.8 and not use the DNS configured on the server.
Update2: I’m currently stuck with the following errors:
Configuring permissions…
Configuration successful
You can now start Umbrel by running:
sudo ./scripts/start
Pulling new containers
Pulling tor_proxy … done
Pulling dashboard … done
Pulling manager … error
Pulling nginx … done
Pulling auth … error
ERROR: for manager Get “https://registry-1.docker.io/v2/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
ERROR: for auth Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
ERROR: Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Get “https://registry-1.docker.io/v2/”: context deadline exceeded
Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Get “https://registry-1.docker.io/v2/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
== End Update Script 01-run.sh ==
== Begin Update Script 02-run.sh ==
Update3: FIX: Hardcoded DNS is the problem here but it oddly only shows as errors on a few containers when updating. You absolutely need to allow full DNS out to either one.one.one.domain or Google. Local DNS will only work for about 85% of update as this is currently coded! Once I opened up FW rules to allow Google DNS to flow everything updated as normal.
