Hey there,
Are there plans to to be able to push images privately à-la GHCR?
Cheers
Yes, its already supported. https://forgejo.org/docs/v16.0/user/packages/container
Sorry,
Maybe I edited my message too late.
My account visibility is set to limited, and it’s not enough to make images I push to the registry private, as I was able to pull a test image from another account.
Cheers
Packages are owned by an organization. The org visibility settings apply here to all packages. There might surely be an issue about this in the Forgejo repo.
I don’t think we are planning any changes on this area.
If you want private packages, you need to create a dedicated org for this (assuming your code and the org owning it should stay public).
Ah gotcha, did not know this was an option.
It seems I can achieve what I want with a private org in addition to my account with private repos.
Thanks for the support 
What about Renovate’s access to images stored in said private registry? Currently, Renovate can’t detect new versions of my private images in other repos.
Do I need to configure it with a token? Is something missing on the platform side?
Cheers
Yes, this doesn’t work right now as this requires granular scoped access for each Renovate job to the respective private assets of the invoking account.
This isn’t entirely impossible but not so easy to implement. We already need to run a forked version of the operator as Forge RBAC and login aren’t supported (only plain OIDC is) and this request would be another custom feature then.
We’ll get back you once there is an option to make this happen.
In the meantime, you could run your own Renovate jobs on schedule as a workaround. In there, you could hand over credentials which allow accessign your private registries.
1 Like