Private registry management about portainer

[galindro]

Nice guys! I want this feature too.

[deviantony]

@MorphBonehunter
This feature will be available as an extension in the next two months.

[PedroMD]

Been waiting for this for a long time! Current open-source GUI projects are either too ugly or difficult to setup. A simple GUI in a portainer way of doing things would be awesome.

Are you thinking of adding native basic auth support (https://docs.docker.com/registry/deploying/#restricting-access)?

[pozylon]

Hi guys, I just wanted to share what I'm using at the moment if you haven't seen this one here:
https://github.com/mkuchin/docker-registry-web

Ideally portainer would also act as an authentication provider to the private registry like that great tool above.

[deviantony]

@PedroMD yes, native basic auth will be supported.

[PedroMD]

Good to know - thank you!

[sabareeshkkanan]

This will be great future . Let me know how i can be helpful

[deviantony]

@sabareeshkkanan you can propose a mockup in the UI via a PR, purely front-end. This would help us decide how to create the best UX for this feature.

[acejam]

This would be amazing.

[sabareeshkkanan]

@deviantony I am sorry i got busy and i cant work on it for at least one more month

[timiil]

great feature.

little hope:
we can write some description for every repository (just like the markdown sub page in every repo in docker hub)

[MorphBonehunter]

Yesterday i found this one https://github.com/Evedel/bow.
As this is also an GO Tool for manage private registries, maybe this one could be used as some "base" for this feature request?

[sabareeshkkanan]

@MorphBonehunter The new version of protainer already has registry management.

[MorphBonehunter]

@sabareeshkkanan maybe i'm wrong but the latest release add management oft registries for using with credentials. This one is for management of management oft images inside private registries.
And in #930 it is mentioned in the comments that this is an seperate task?

[deviantony]

@MorphBonehunter is right, this will come later this year.

[zwx168238]

hi may i know what's the status about this feature.
now i use 1.14.0.now we still use our custom registry.

[deviantony]

Hey @MorphBonehunter

There is no work on this feature yet, the goal here is to allow the management of images inside private/custom registries.

Currently, 1.14 allows you to connect to your private/custom registries using credentials.

[MorphBonehunter]

Hey @deviantony, i think this was an comment for @zwx168238 😄

[deviantony]

woops you're right :-)

[zwx168238]

@deviantony ths .i will try ASAP if got any new details will let you know

[ibnesayeed]

If private registry management is to be provided, it would also be great to have automated build feature (similar to DockerHub) from sources like GitHub/BitBucket or any Git server (such as Gitlab, Gitea, or Gogs etc.) that allows webhooks. When designing the UI for automated builds, we should consider adding fields that enable supplying build-args.

[MorphBonehunter]

@ibnesayeed maybe i understand this wrong but i would say this is a little bit out of scope.
for my understanding registry management is for viewing/delete docker images inside an private registry (something like this).
what you want i think is an CI/CD Tool like drone or the build in from gitlab.

[acejam]

@ibnesayeed I would have to agree with @MorphBonehunter. If you're setting up a private Docker registry and using Portainer to help manage it, odds are you're also running a build server for CI/CD, which is where images should be built in the first place.

[ibnesayeed]

I understand that the process of building the image itself is out of scope of Portainer, that is the job of a CI system, but the same is true about the registry too. Portainer is not implementing yet another Docker registry, it is just going to provide a management interface on top of existing registries, so why can't it provide interface for build systems. In my opinion, limiting the definition of "registry management" to just viewing and deleting is too restrictive; creating, pulling, synchronizing, tagging, scanning, and visualizing images, all count towards the Docker image management. Features should be pluggable, for example, registry data and controls will only show up when a registry is linked, similarly, build related components would show up only if a build server is linked. Even if we have a CI/CD system configured, opening a separate interface to build images, then using Portainer for the rest of the task would present a disconnect.

That said, not everything can be implemented overnight, so certain important features can be prioritized, but the architecture of the new implementation should consider possible extensions in future and design accordingly.

[MorphBonehunter]

hey @WTFKr0 & @deviantony, what about this one.
It' seems there is only one point left (Delete option to remove a repository) or is the blocker the
distribution/distribution#2434 ?
I would also test the pr, but the portainer/portainer:pr1656 seems not exist anymore

[ibnesayeed]

Registry management can now utilize the newly implemented webhooks system (#1663) to implemented DockerHub-like Automated Build system.

[deviantony]

Registry manager extension released with 1.20.0 and now publicly available.

[fenchu]

I can verify v1.20 works with sonatype nexus3 v3.14-03 login. great work :-)

[ncresswell]

Excellent, thank you. Will will note that. Rgds, Neil Cresswell On 20/12/2018, at 2:07 AM, fenchu <[email protected]<mailto:[email protected]>> wrote: I can verify v1.20 works with sonatype nexus3 v3.14-03 login. great work :-) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_56-23issuecomment-2D448590944&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=yGCmP5tAulb7SmKs12tsp0Dfvk7IylbzAReuob1lSKs&s=ywe6HBgRFL7dCymw14VQmbO8D_4qXF_1oQi-3N0HeSM&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlQmkkHnmebzGu7Sd4iEsdlacEchfks5u6joigaJpZM4JJ4Mj&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=yGCmP5tAulb7SmKs12tsp0Dfvk7IylbzAReuob1lSKs&s=_HjcGUHlN7d3AhmkL2lEBml64cHCdqQzRFfEeFZYYOg&e=>.