Docker registry

[mario]

I got the registry working, need to get it integrated with GitLab now.

[girish]

@mario Did you get the registry working as a Cloudron package or outside Cloudron?

[Lonkle]

@mario What he said ^^^

[robi]

anyone check his gitlab repo?

[Lonkle]

@robi I don't know it.

[mario]

@girish as a Cloudron package. I'll push it to gitlab once I clean it up, but it's useless to me without the GitLab integration and that part seems tricky.

[mario]

@girish
https://git.cloudron.io/mario/docker-registry

[mario]

default user:

admin/admin

[mehdi]

@mario This looks good ! Combined with the authProxy of Cloudron6, we could disable the htpasswd auth of the app and since it uses basic auth it should work with the LDAP users !

We would just have to slap a basic web interface on that and it would be perfect

[mario]

@mehdi I'm updating it further now with redis support etc.

[mario]

Updated and working.

[robi]

Amazing progress, thank you @mario

Now to figure out how to install this and inch another step in packaging a custom app..

[fbartels]

@mario would you mind me making an attempt of adding https://github.com/Joxit/docker-registry-ui/ to your app? Or would you rather do it yourself, or choose a different ui?

Another solution could be the reg cli utility. A simple docker binary that can also expose a ui.

@robi after you installed to Cloudron cli (should be on a Linux machine with docker installed) you just need to run cloudron build && cloudron install and then follow the prompts.

[mario]

@fbartels honestly, I'd prefer UI as a separate app and would attempt Portus - possibly together with you. What are your thoughts?

An alternative would indeed be, if people prefer, to have Registry + UI together -> but in any case I'd strongly prefer Portus to anything else.

[girish]

@mario Oh wow, this is awesome. I had no idea one could run a registry this way. I thought one has to make some use of the docker addon! This way is so much simpler and nicer.

I forked the code to https://git.cloudron.io/cloudron/docker-registry-app/ and gave you permissions. It just worked (tm). Do you think you can put in a LICENSE file and keep developing there? It's a holiday for thanksgiving here, but I will look into this soonish.

[fbartels]

@mario TIL portus does not implement it's own registry, but simply uses the official one.

Yes, having them separate can have it's benefits. Would need to refresh my knowledge in regards to portus first before I know if I could be of much help.

[mario]

@girish happy Thanksgiving!

Thanks for the fork, will see what I can do in the coming days

[girish]

@mehdi said in Docker registry:

Combined with the authProxy of Cloudron6, we could disable the htpasswd auth of the app and since it uses basic auth it should work with the LDAP users !

I gave this a try and this worked great! https://git.cloudron.io/cloudron/docker-registry-app/-/commit/547e3b30b0d9038d9fe73416a7df7b3d32f265ec

[mario]

@fbartels said in Docker registry:

@mario TIL portus does not implement it's own registry, but simply uses the official one.

Yes, having them separate can have it's benefits. Would need to refresh my knowledge in regards to portus first before I know if I could be of much help.

Indeed It basically takes advantage of the official registry support for token-auth, giving you a nice UI, permissions, etc.

When you get a moment to check it out, let's talk!

[mario]

@girish said in Docker registry:

@mehdi said in Docker registry:

Combined with the authProxy of Cloudron6, we could disable the htpasswd auth of the app and since it uses basic auth it should work with the LDAP users !

I gave this a try and this worked great! https://git.cloudron.io/cloudron/docker-registry-app/-/commit/547e3b30b0d9038d9fe73416a7df7b3d32f265ec

The only problem here is that this would not work for me - we basically only have admins on Cloudron itself, and this would limit Registry access to them alone.

Edit: this is because we do auth via Azure AD/SAML for pretty much everything in the company.