No delete option for repo or tag ??

[timconsidine]

Nervous to ask because probably revealing my stupidity.
I have been using Docker Hub as my docker repository but it is has limit on private repositories.
So I am trying the Docker Registry app from Cloudron App Store.
Installed.
Pushed a test build to it.
Can see it listed in the app interface.
But I cannot see an option to delete it in the UI.
Is there one ? Do I need use the CLI to remove it ?

[BrutalBirdie]

@timconsidine you can use the file manager and just delete the folder

---

Example, I wish to delete the com.odoo.cloudronapp repo from the registry.
I just delete /app/data/storage/docker/registry/v2/repositories/com.odoo.cloudronapp.
Rest will be handled by the garbage collector.
https://docs.cloudron.io/apps/docker-registry/

---

@timconsidine said in No delete option for repo or tag ??:

Nervous to ask because probably revealing my stupidity.

Nah all good. Never be afraid to ask questions.
How should one know how to handle this task if one never hosted a docker registry.
I would also expect a delete button with all the option you get with cloudron

Maybe we could add that to the docs.

[timconsidine]

@BrutalBirdie thank you! Nice and easy solution. I like those

Follow-up : I also don't see a way to set a repo to be private.
Is it correct understanding that it's automatically private because it's in my private registry ?
i.e. someone would need to log in to the registry to see images and download them

[BrutalBirdie]

@timconsidine

@timconsidine said in No delete option for repo or tag ??:

Is it correct understanding that it's automatically private because it's in my private registry ?
i.e. someone would need to log in to the registry to see images and download them

Exactly.
If you choose the cloudron user management, then a login is needed to access the whole registry.
No sure if there is an option for per-user repositorys (That would be a separate topic tho)

[timconsidine]

@BrutalBirdie that's fine.
Yes, I'm using Cloudron user management and restricting access with that.
I don't need per-user repos.
If I did, I would probably set up a separate instance of the app and restrict it by user.

Cool, thank you. Now I will de-docker-hub myself !

[BrutalBirdie]

@BrutalBirdie said in No delete option for repo or tag ??:

Maybe we could add that to the docs.

Created a PR for that information.
https://git.cloudron.io/cloudron/docs/-/merge_requests/39
@staff

[girish]

@timconsidine said in No delete option for repo or tag ??:

But I cannot see an option to delete it in the UI.

From https://github.com/Joxit/docker-registry-ui#faq ,

I deleted images through the UI, but they are still present on the server. How can I delete them?
When you delete an image with the UI, only the reference is deleted and not the content.
To remove dangling images, you need to run the garbage collector of the registry with the command registry garbage-collect config.yml or docker exec registry registry garbage-collect config.yml. (see #77 #147)

Is this what you hit? Or do you not even see the delete option in the UI?

[BrutalBirdie]

@girish there is no delete button.

[girish]

@BrutalBirdie mm, apparently, it's disabled by default: https://github.com/Joxit/docker-registry-ui#available-options .

DELETE_IMAGES: Set if we can delete images from the UI. (default: false)

Not seeing any reason to keep it disabled.

[BrutalBirdie]

@girish Hmm I did not even consider looking there, since I did not look into the app which ui is used

Since there are more option that could be used via variables maybe include an .env file which gets dynamically loaded on the start.
Similar to what I did with greenlight.

[girish]

@BrutalBirdie said in No delete option for repo or tag ??:

Since there are more option that could be used via variables maybe include an .env file which gets dynamically loaded on the start.

Agreed! Just fixing up the package now.

[girish]

Pushed an update for this. To keep it simple, I just enabled it depending on the delete config for the registry itself (where it is enabled by default).