Closed johnnashautomation closed 1 week ago
johnnashautomation
commented
3 months ago I just realized that the postgres version is different in compose file and in the logs. This could be one of the issue?
Image I use for postgres -> postgres:13.6-alpine Log -> starting PostgreSQL 14.11 on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bi
yrzr
commented
2 months ago I think you should set "postgresql['enable'] = false;" to disable the Postgres inside the gitlab container in order to use an external one.
And Postgres 13 will no longer be supported after Gitlab 17.0.0 https://docs.gitlab.com/ee/administration/package_information/postgresql_versions.html
johnnashautomation
commented
2 months ago I did it. also I changed postgres image version to 14.11-alpine. Deleted all mounted folders and re-created with 'docker-compose up -d' command. Once everything was created and I pushed repo and restarted docker itself. I still have the same result.
Updated compose file
gitlab: image: 'yrzr/gitlab-ce-arm64v8:latest' restart: unless-stopped hostname: 'gitlab.local' container_name: gitlab-ce privileged: true depends_on:
yrzr
commented
2 months ago What about deleting the volumes and trying again?
berkercakici
commented
2 months ago What about deleting the volumes and trying again? gitlab-ce-conf gitlab-ce-logs gitlab-ce-data gitlab-db-data
When I delete all folders above it starts like fresh installation without any issue. Then I again login and push a repository and if I stop docker-compose and restart nothing happen. The issue happen after I restart docker or pc. Once docker start It's like something is changing.
After I searched I found solution like that but it's not also works.
Changing from VirtioFS to gRPC FUSE and check Use Virtualization framework
johnnashautomation
commented
2 months ago Do you have any clue about how to fix this issue @yrzr ? I also tried to the docker run command I have same issue in Apple Silicon.
docker run \ --detach \ --restart unless-stopped \ --name gitlab-ce \ --privileged \ --memory 8G \ --publish 22:22 \ --publish 80:80 \ --publish 443:443 \ --hostname gitlab.example.com \ --env GITLAB_ROOT_PASSWORD="YourPasswordHere" \ --env GITLAB_OMNIBUS_CONFIG=" \ registry['enable'] = false; \ GITLAB_OMNIBUS[your_other_configs] =options; "\ --volume /srv/gitlab-ce/conf:/etc/gitlab:z \ --volume /srv/gitlab-ce/logs:/var/log/gitlab:z \ --volume /srv/gitlab-ce/data:/var/opt/gitlab:z \ yrzr/gitlab-ce-arm64v8:latest
yrzr
commented
2 months ago Try this
docker run \
--detach \
--restart unless-stopped \
--name gitlab-ce \
--privileged \
--memory 8G \
--publish 22:22 \
--publish 80:80 \
--publish 443:443 \
--hostname gitlab.example.com \
--env GITLAB_ROOT_PASSWORD="YourPasswordHere" \
--env GITLAB_OMNIBUS_CONFIG=" \
registry['enable'] = false; "\
--volume /srv/gitlab-ce/conf:/etc/gitlab:z \
--volume /srv/gitlab-ce/logs:/var/log/gitlab:z \
--volume /srv/gitlab-ce/data:/var/opt/gitlab:z \
yrzr/gitlab-ce-arm64v8:latest
0x1af2aec8f957
commented
1 month ago Changing from VirtioFS to gRPC FUSE and check Use Virtualization framework
@berkercakici This worked for me!
vguleaev
commented
1 week ago What about deleting the volumes and trying again? gitlab-ce-conf gitlab-ce-logs gitlab-ce-data gitlab-db-data
When I delete all folders above it starts like fresh installation without any issue. Then I again login and push a repository and if I stop docker-compose and restart nothing happen. The issue happen after I restart docker or pc. Once docker start It's like something is changing.
After I searched I found solution like that but it's not also works.
Changing from VirtioFS to gRPC FUSE and check Use Virtualization framework
you are my saviour ! 🙇
Once I install everything works smootly but after I restart to docker it can not connect to database anymore and I keep in the loop for restarting gitlab-ce
OS macstudio m2 max I don't have dns configuration or firewall settings to block docker
I have checked postgres is up and runing
docker-compose I use
After restart docker and restart compose file again and check the docker-ce gitlab-ctl status shows
Then I restart the gitlab-ctl but no luck
Logs in gitlab-ce container