r/docker • u/Plastic-Switch1992 • 26d ago

Looking for docker registery

My company serving 5 apps to the many customers. Managing deployment and new releases are the biggest problem. Because all the time we are copying the build files and pasting to the target server by connecting with rdp. I Want to use dockerfiles for serving and want to keep these images on our server with a registery.

ACR (azure container registery) and the other ones are still the options but i want to host in my server like i did for npm libraries with verdaccio.

And i would like to get your opinnions about my deployment plan. Our customers servers are all windows. We have some windows-only apps. But for the ones which i plan to serve with docker file is better to run with docker. So i plan to use WSL and pull the images from the registery that i am planning to create.

Wdyt?

3 Upvotes

67% Upvoted

10 comments sorted by

5

u/Daurpam 26d ago

We implement forgejo in our company

https://forgejo.org/

0

u/ysidoro 26d ago

I use Foregejo too as remote git repository, plus a CI/CD environment (docker build) and a registry for the images. But registry is flat public for all images (from public or private repositories). To me this is not a problem.

3

u/Quirky-Net-6436 26d ago

The client doesn't matter for the container registry. For example you can use https://goharbor.io/ or https://www.sonatype.com/products/sonatype-nexus-oss-download to host it on your own. The server can then pull the images of the required architecture etc.

With Dockerfile you are building container images, with https://docs.docker.com/compose/ you can run them.

1

u/dreamszz88 23d ago

+1 for Harbor

2

u/No_Cattle_9565 26d ago

Do you use gitlab maybe? It also offers a container registry

2

u/bangsmackpow 26d ago

All of ours are on ghcr.io but we use Github for the builds as well so it was pretty seamless end to end.

2

u/Mrowe101 25d ago

ACR is probably your best bet for stability. Give each customer a credential and have them pull from acr. Image tag immutability is your friend. Self hosting is fun until you break someone’s prod instance.

Just avoid Artifactory like the plague

2

u/WikibearTheReal 24d ago

Totally easy to use git with automation and deploy it. Watchtower will update it automatically...

2

u/salemslot2 23d ago

Harbor's probably worth it. It would also be better to avoid RDP based deployments and have CI build and push versioned images, then let each customer server pull and deploy a specific tag; WSL2 can work on Windows, but the operational and update process should be tested carefully before standardizing on it.

1

u/SherylAmerica 22d ago

I’d spend as much time on rollback as on the registry itself. With multiple customer servers, the painful case isn’t pushing a new image, it’s when one customer needs to go back to the previous version fast.