3 ms·

I don't think your concerns are founded, I just deployed GitLab for personal use on a virtual machine with the omnibus image (gitlab-ce:latest) and it worked fl

I don't think your concerns are founded, I just deployed GitLab for personal use on a virtual machine with the omnibus image (gitlab-ce:latest) and it worked flawlessly. And since they released an update today, to upgrade all I had to do was: docker pull gitlab/gitlab-ce:latest docker stop gitlab docker rename gitlab gitlab-old docker run --detach --publish 60100:80 --publish 58432:22 --name gitlab --restart always \ --volume /var/volumes/gitlab/config:/etc/gitlab \ --volume /var/volumes/gitlab/logs:/var/log/gitlab \ --volume /var/volumes/gitlab/data:/var/opt/gitlab \ gitlab/gitlab-ce:latest # after verifying the new image works, docker rm docker-old; docker rmi [old image]. It took less than an hour to configure it for external SMTP relay, external auth with two factor authentication, etc. I did just get started with it, but I have to say the omnibus install was fairly easy.

contingencies 10y ago
Great, I'm glad it worked for you. It didn't work for me and other people, as per the issues linked. When it doesn't work, there's no clearly defined debug path, and very little response.
- AaronFriel 10y ago
  Respectfully, it seems like you are using the wrong Docker image, and that's the source of your troubles. Others have commented similarly, and I think that you are too easily dismissing them.
  - sytse 10y ago
    I think you're right Aaron. The Sameer docker image used to be the only way to run GitLab with Docker but we don't recommend it and it is no longer listed on our installation page https://about.gitlab.com/installation/ https://about.gitlab.com/installation/ to prevent confusion. Also see my answer in https://news.ycombinator.com/item?id=13243443 https://news.ycombinator.com/item?id=13243443
supergreg 10y ago
I tried the docker image for gitlab-ce just 2 days ago and had to exec bash into it and chmod a workhorse socket file to get it working. Glad they fixed it.

contingencies 10y ago

Great, I'm glad it worked for you. It didn't work for me and other people, as per the issues linked. When it doesn't work, there's no clearly defined debug path, and very little response.

AaronFriel 10y ago
Respectfully, it seems like you are using the wrong Docker image, and that's the source of your troubles. Others have commented similarly, and I think that you are too easily dismissing them.
- sytse 10y ago
  I think you're right Aaron. The Sameer docker image used to be the only way to run GitLab with Docker but we don't recommend it and it is no longer listed on our installation page https://about.gitlab.com/installation/ https://about.gitlab.com/installation/ to prevent confusion. Also see my answer in https://news.ycombinator.com/item?id=13243443 https://news.ycombinator.com/item?id=13243443

supergreg 10y ago

I tried the docker image for gitlab-ce just 2 days ago and had to exec bash into it and chmod a workhorse socket file to get it working. Glad they fixed it.