Container registry
-
Sounds good improvment.
I might be being bit thick, but how does the new registry with build functionality align with the traditional advice "do not build on your primary Cloudron instance" ?
Is the traditional advice now revoked ?Indie app dev, scratching my itches : communityapps.appx.uk, portfolio at myca.appx.uk
-
I have tested the new registry and it works excellently for me. I am quite happy, and have already replaced my older workflows with the builder and the private docker registry as separate apps.
@ekevu123 thanks for testing! let us know if you miss a feature, currently the feature set is very much around what we wanted for our own packages. But all of Cloudron packages are now built and hosted on this new registry. I think we will switch the fallback from quay to our selfhosted registry at some point.
-
Sounds good improvment.
I might be being bit thick, but how does the new registry with build functionality align with the traditional advice "do not build on your primary Cloudron instance" ?
Is the traditional advice now revoked ?@timconsidine I should have probably highlighted that aspect since it's hidden in the "Builds run in-app with BuildKit (not the host Docker daemon)" line. Previous registry used to build using the host docker (the host docker socket was exposed to the app). If you build some mega app, it will bring down the server.
With this new registry, the builds are sandboxed to the app - so the app's cpu and memory limits apply. The host docker storage is not polluted.
-
@timconsidine I should have probably highlighted that aspect since it's hidden in the "Builds run in-app with BuildKit (not the host Docker daemon)" line. Previous registry used to build using the host docker (the host docker socket was exposed to the app). If you build some mega app, it will bring down the server.
With this new registry, the builds are sandboxed to the app - so the app's cpu and memory limits apply. The host docker storage is not polluted.
@girish thanks for the explanation.
Currently I do dev work on my Mac laptop, use
docker build --context build-server ...to run builds and registry pushes on a small VPS, avoids impact on my laptop and on my Cloudron box.I will get brave and try out container registry sometime
-
G girish referenced this topic
-
G girish forked this topic
-
@timconsidine I should have probably highlighted that aspect since it's hidden in the "Builds run in-app with BuildKit (not the host Docker daemon)" line. Previous registry used to build using the host docker (the host docker socket was exposed to the app). If you build some mega app, it will bring down the server.
With this new registry, the builds are sandboxed to the app - so the app's cpu and memory limits apply. The host docker storage is not polluted.
-
Ah so essentially this: https://forum.cloudron.io/topic/1977/platform-data-and-other-disk-usage/26
I guess the community authors would have to chime in, if they see this as needed/useful.
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