3 ms·
This image is very good but we recommend the one based on the Omnibus Packages https://gitlab.com/gitlab-org/gitlab-ce/tree/master/docker https://gitlab.com/git
by sytse 12y ago
This image is very good but we recommend the one based on the Omnibus Packages https://gitlab.com/gitlab-org/gitlab-ce/tree/master/docker https://gitlab.com/gitlab-org/gitlab-ce/tree/master/docker
I plan to make these official on Dockerhub over the weekend. But if there are vulunteers that want to keep them up to date that would be perfect.
- nickstinemates 12y agoSend me an email - nick@docker.com - I'll make sure you get connected to the right team.
- sytse 12y agoThanks! Just send you an email.
- teraflop 12y agoOut of curiosity, why do you recommend running an Omnibus container instead of separate containers for Gitlab, Postgres and Redis? It seems like it only gains a tiny bit of convenience (one "docker run" command instead of three), and you lose a lot of flexibility to move things around and reconfigure later on. What if I want to run multiple frontend instances, or keep a warm standby database replica?
- sytse 12y agoThe main reason is that the Omnibus package setup has additional logic to respawn workers that are using too much memory. I also like that it uses a separate data container to store everything.
- codereflection 12y agoIn the https://github.com/sameersbn/docker-gitlab https://github.com/sameersbn/docker-gitlab container, you can mount volumes from the Docker host to store data as well, and it also uses linked containers for Redis and Postgres. The respawn workers logic does seem important though. Does the manual gitlab install also handle situation?
- sytse 12y agoNo, the manual install doesn't handle that. It requires Runit if I remember correctly.
- mrmondo 12y agoThe official omnibus packages do work very nicely - I can't say I've had any problem with them since they came out!
- sytse 12y agoGood to hear that!