Unusable application
-
I'm guessing 9.1.3 rendered the application unusable, as the issue appeared later than the latest update of this app.
Pushing/pulling an image from a remote works correctly. However, attempting to pull an image from the same server doesn't work at all.
For instance:
- I have a registry @ registry.cloudron.local
- I have an app @ app.cloudron.local, using an image from the registry, on the same cloudron.
Whenever I attempt to update this application with a new image, the pull never works.
Mar 19 18:51:04 box:docker Attempt 1 failed. Will retry: Unable to pull image registry.cloudron.local/app.image:2.0.13. registry error: {"reason":"server error","statusCode":500,"json":null}In the registry configuration in Cloudron settings, the error
Invalid serverAddress: socket hang upappears whenever I attempt to save the private registry settings.In the registry application logs, there is the following line, appearing intermittently:
Mar 19 20:32:18 time="2026-03-20T00:32:18.895638941Z" level=error msg="traces export: Post \"https://localhost:4318/v1/traces\": dial tcp [::1]:4318: connect: connection refused" go.version=go1.23.7 instance.id=redacted service=registry version=3.0.0I have multiple Cloudrons, all with a registry application installed and facing the same issue.
As mentioned in the beginning of my topic, pulling from a remote works.
Connecting the private registry
registry.cloudron.localinmy.other-cloudron.localworks perfectly. It seems like there might be a DNS issue.Feel free to ask for more information.
-
I'm guessing 9.1.3 rendered the application unusable, as the issue appeared later than the latest update of this app.
Pushing/pulling an image from a remote works correctly. However, attempting to pull an image from the same server doesn't work at all.
For instance:
- I have a registry @ registry.cloudron.local
- I have an app @ app.cloudron.local, using an image from the registry, on the same cloudron.
Whenever I attempt to update this application with a new image, the pull never works.
Mar 19 18:51:04 box:docker Attempt 1 failed. Will retry: Unable to pull image registry.cloudron.local/app.image:2.0.13. registry error: {"reason":"server error","statusCode":500,"json":null}In the registry configuration in Cloudron settings, the error
Invalid serverAddress: socket hang upappears whenever I attempt to save the private registry settings.In the registry application logs, there is the following line, appearing intermittently:
Mar 19 20:32:18 time="2026-03-20T00:32:18.895638941Z" level=error msg="traces export: Post \"https://localhost:4318/v1/traces\": dial tcp [::1]:4318: connect: connection refused" go.version=go1.23.7 instance.id=redacted service=registry version=3.0.0I have multiple Cloudrons, all with a registry application installed and facing the same issue.
As mentioned in the beginning of my topic, pulling from a remote works.
Connecting the private registry
registry.cloudron.localinmy.other-cloudron.localworks perfectly. It seems like there might be a DNS issue.Feel free to ask for more information.
-
@lanhild I just tried to reproduce this and it seems to work fine. Have you added the local registry app as a Private docker registry i.e under System -> Docker -> Registries? The local registry app is not automatically available for app install (same cloudron or different cloudron).
-
@lanhild I just tried to reproduce this and it seems to work fine. Have you added the local registry app as a Private docker registry i.e under System -> Docker -> Registries? The local registry app is not automatically available for app install (same cloudron or different cloudron).
-
In the registry configuration in Cloudron settings, the error Invalid serverAddress: socket hang up appears whenever I attempt to save the private registry settings.
OK, I missed this one. Can you try
docker loginon the server itself and see if that works ? -
In the registry configuration in Cloudron settings, the error Invalid serverAddress: socket hang up appears whenever I attempt to save the private registry settings.
OK, I missed this one. Can you try
docker loginon the server itself and see if that works ?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login