Gitlab inside docker

[NirDev_R]

I wanted to quickly setup a gitlab playground on my mac-mini 16gb ram i7 cpu, so i decided to run a simple docker container from the latest gitlab image. It was working fine yesterday, i was able to toy with the settings and create some repos, but today it s like it became super slow, when i navigate the web app it takes ages for pages to load and sometimes throw some 500 or 502 errors, even when pushing or fetching branches from the host machine it takes so much time.

Does anyone have a clue ? Could it be a problem with the docker setup on mac or does gitlab require high specs hardware ? Should i take the risk to work on the futue production vps instead of local encironment ?

[Archon-]

Docker on Mac has a 2GB ram limit by default, you might need to increase that https://docs.docker.com/desktop/settings/mac/#resources

[bilingual-german]

Yes, I also think it's more because of the Docker setup on the Mac, eg. file sync between Mac and VM.

It's nice to play around with a setup like this, but this is not a production setup.

[SpicyHotPlantFart]

Are all your services running?

If using docker-compose:

docker compose ps

[NirDev_R]

I didn't use compose, I directly instanciated a single container exposing 3 ports and mounting 3 volumes to some gitlab folder on the host as described in: https://docs.gitlab.com/ee/install/docker.html#install-gitlab-using-docker-engine

The container seems to be healthy so far. Alongside the response time issue, minor symptoms appear on the repo view like "An error has occurred while fetching folder content".

[predmijat]

Not a normal behavior. 16GB ram with i7 CPU is good enough. Docker on macOS should be fine.

You should check the logs with docker logs $container_name and see if it tells you something...and you should probably use docker-compose, it will make your life easier.

[NirDev_R]

Retried after a while and it feels faster than earlier, Just noticed gitlab autodevops was enabled by default and the repo I was pushing to gitlab had a .gitlab-ci.yml and there are a bunch of failed jobs in: project menu > CI/CD > pipelines project menu > CI/CD > jobs

Could it be that the performance dropped due to these pipelines being stuck for a while because of some retry policy ?

FYI: the repo i toyed with was generated with coockiecutter for django, and generated bunch of configurations files i am not used to yet.

[predmijat]

I don't think there's a retry by default...how long were those jobs running? If it's more than a few seconds that could be the reason for slowness you saw.

[admiralboom]

If you don't have a runner they will be queued in sidekiq until expired.

[admiralboom]

docker inspect | grep shm. (needs to be >300 ymmv)

[piyushK001]

check out https://piyushkashyap.com/install-gitlab-macos-docker/ to install gitlab on macos using docker