Gitlab install fails consistently due to missing Docker container

[hovinen]

When I attempt to install Gitlab on my instance, I get the following error:

An error occurred during the install operation: Docker Error: (HTTP code 404) no such container - No such image: cloudron/com.gitlab.cloudronapp:20230312-065100-441837260

This has happened consistently for the past three days. Retrying does not help, nor does deinstalling and reinstalling.

Could you please fix this? Thank you.

[nebulon]

Have you configured anything on the docker side regarding repositories?

Also can you try to pull the image via SSH by running:

docker pull cloudron/com.gitlab.cloudronapp:20230312-065100-441837260

[girish]

I am guessing this is something DNS related. Can you check the status of unbound ? Cloudron Dashboard -> Services . Is unbound green ? (unbound is our internal DNS server).

[hovinen]

@girish Thanks for your reply.

unbound is green, as are all other services on the dashboard.

I'm also able to install other apps without difficulty. This appears to be specific to Gitlab.

The only thing which isn't working is email, but I don't see how that should be related.

[hovinen]

@nebulon Thanks for your reply.

I haven't touched any of the configuration on Docker.

However, the docker pull command worked.

I will try again this evening to see whether the problem is still present.

[girish]

Tried this again now and the image is very much there.

$ docker pull cloudron/com.gitlab.cloudronapp:20230312-065100-441837260
20230312-065100-441837260: Pulling from cloudron/com.gitlab.cloudronapp
e96e057aae67: Already exists 
f319501191fe: Already exists 
....
602a6d78f16d: Pull complete 
Digest: sha256:854bdc340d7434da03c7fb0c85c844b1351f3046682add688944b7f4a2a70fd0
Status: Downloaded newer image for cloudron/com.gitlab.cloudronapp:20230312-065100-441837260
docker.io/cloudron/com.gitlab.cloudronapp:20230312-065100-441837260

https://hub.docker.com/layers/cloudron/com.gitlab.cloudronapp/20230312-065100-441837260/images/sha256-854bdc340d7434da03c7fb0c85c844b1351f3046682add688944b7f4a2a70fd0?context=explore is the image itself

[hovinen]

I tried again this evening and got the same 404 error.

However, I noticed when I did the manual docker pull that the volume on the server was running low on space. I rectified that and retried, after which the installation worked.

I'm not sure how a lack of space could be related to a 404 error, but it's working now.

Thanks for your help!

[girish]

@hovinen Ah yes! docker returns 404 it seems when it doesn't have enough disk space to store images. I remember this (again) now. Unfortunately, the API has no way of detecting this.