Cloudron Install fails.
-
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 resolutionI 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?
@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
--redois just a workaround for the moment, I am trying to get to the root cause. -
@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
--redois just a workaround for the moment, I am trying to get to the root cause.@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 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?
@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
--redoworks later). -
@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
--redoworks later). -
@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
--redois just a workaround for the moment, I am trying to get to the root cause. -
@girish home network. Same home network as the previous cloudron which is still working
-
@Mastadamus Once installed, it's all good. this is just a one time install issue.
@girish yeah it seems to be working great now. Also kudos to your migration process. Restoring from backup was not 2 bad
-
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 dockerI 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!
-
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 dockerI 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!
-
@DadsHockeyLife Which VPS provider are you using?
@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.
