Cloudron Install fails.

[Mastadamus]

Ubuntu 20.04 LTS fresh build. I am trying to rebuild my cloudron on a new server which I will then restore from backup .

I keep getting to the spot where it downloads containers then I get the following error message:

for image in ${images}; do
docker pull "${image}"
docker pull "${image%@sha256:}" # this will tag the image for readability
done
Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution
"https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolutionfor image in ${images}; do
docker pull "${image}"
docker pull "${image%@sha256:}" # this will tag the image for readability
done
Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution
"https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: Temporary failure in name resolution

I can curl "https"//registry-1.docker.io/v2/ from the CLI after the script fails and it returns:

{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}

So this makes me think name resolution is good?

Any help?

[nebulon]

once it failed, are you able to resolve registry-1.docker.io ? You can run host registry-1.docker.io via SSH to check this. If this is not working, then check systemctl status unbound which is the local DNS resolver Cloudron is installing.

[Mastadamus]

@nebulon I could resolve it.

I ran the install script again with --redo and it worked.

[girish]

@Mastadamus Can you tell me a bit more about your server? It is on a VPS (if so, which one) or is it on a home network?

The --redo is just a workaround for the moment, I am trying to get to the root cause.

[robi]

@girish looks like it's flaky DNS.

Perhaps you need to have the install script prime all the DNS names referenced in the script?

Or set a specific DNS server for the duration of the install?

Or check that all DNS download locations are reachable before continuing?

[girish]

@robi initially, I thought it was flaky DNS too. But I think this is almost like the 5th bug report of the same kind on different networks which makes me think there is something wrong in our install script. I think something about installing unbound+resolvconf makes things go down for a short while (this is why --redo works later).

[robi]

@girish ah, maybe it's a sequencing issue, do the unbound install after the downloads?

[Mastadamus]

@girish home network. Same home network as the previous cloudron which is still working

[girish]

@Mastadamus Once installed, it's all good. this is just a one time install issue.

[Mastadamus]

@girish yeah it seems to be working great now. Also kudos to your migration process. Restoring from backup was not 2 bad

[DadsHockeyLife]

I had this same issued today as I tried to install on a fresh Ubuntu Server install (20.04). The fix I found was this....

https://appuals.com/cannot-connect-to-the-docker-daemon-at-unix-var-run-docker-sock/

I use Termius for terminals, so while the original install was running, I opened a new terminal to the server and ran the following commands....

sudo systemctl unmask docker
systemctl start docker

I then went back to the install (log) window and BAM! It was installing like a champ. I might have to do the --redo command, but I'll check after it's done installing.

Hope this helps someone...Cheers!

[girish]

@DadsHockeyLife Which VPS provider are you using?

[DadsHockeyLife]

@girish I'm not. I'm self hosting. It's running on a Ubuntu 20.04 Server install on a Synology 1517+ with Intel Processor. It's got 4 Cores and 6GB of memory for now.