Issue with Mounting GlusterFS Storage in Docker Compose for GitLab

[Said-devops-tm]

I have set up GlusterFS storage and created a directory on my local host machine, which I then mounted to the GlusterFS storage.

When I mount a directory from my local host machine in the volumes section of the docker-compose.yml file, both the GitLab image and the GitLab Runner deploy successfully without any issues.

However, when I try to mount the GlusterFS storage path in the volumes section of the Compose file, the built-in PostgreSQL instance within the GitLab image fails to mount to the GlusterFS storage. The deployment works fine for GitLab itself, but PostgreSQL encounters problems.

Has anyone experienced similar issues, or could someone provide guidance on how to resolve this?

Here is my compose file (mounted on host machine) works perfectly:

version: "3.6" services: gitlab: image: private.registry.com/docker/gitlab-ce:17.3.6-ce.0 deploy: mode: global placement: constraints: [node.id == ymqksna8bxikggkusfujaunk4] container_name: gitlab restart: always hostname: 'gitlab.example.com' ports:

• "2222:22"
• "80:80"
• "443:443" volumes:
• /srv/gitlab/data:/var/opt/gitlab
• /srv/gitlab/logs:/var/log/gitlab
• /srv/gitlab/config:/etc/gitlab shm_size: '256m' environment: GITLAB_OMNIBUS_CONFIG: "from_file('/omnibus_config.rb')" configs:
• source: gitlab target: /omnibus_config.rb secrets:
• gitlab_root_password gitlab-runner: image: gitlab/gitlab-runner:alpine deploy: mode: replicated replicas: 4 configs: gitlab: file: ./gitlab.rb secrets: gitlab_root_password: file: ./root_password.txt

Here is my compose file (mounted glusterfs storage) fails: version: "3.6" services: gitlab: image: private.registry.com/docker/gitlab-ce:17.3.6-ce.0 container_name: gitlab restart: always hostname: 'gitlab.example.com' ports:

• "2222:22"
• "80:80"
• "443:443" volumes:
• /mnt/glusterfs/data:/var/opt/gitlab
• /mnt/glusterfs/logs:/var/log/gitlab
• /mnt/glusterfs/config:/etc/gitlab shm_size: '256m' environment: GITLAB_OMNIBUS_CONFIG: "from_file('/omnibus_config.rb')" configs:
• source: gitlab target: /omnibus_config.rb secrets:
• gitlab_root_password gitlab-runner: image: gitlab/gitlab-runner:alpine deploy: mode: replicated replicas: 4 configs: gitlab: file: ./gitlab.rb secrets: gitlab_root_password: file: ./root_password.txt

Log says: [2024-11-06T10:31:13+00:00] FATAL: RuntimeError: database_objects[postgresql] (postgresql::standalone line 32) had an error: RuntimeError: postgresql_user[gitlab] (postgresql::standalone line 28) had an error: RuntimeError: execute[create gitlab postgresql user] (postgresql::standalone line 13) had an error: RuntimeError: Exhausted service checks and database is still not available

[pranithk]

I don't think anyone got glusterfs to work correctly with database to my knowledge.

[Said-devops-tm]

Hi sir, Thanks for your response! Could you please recommend High Availability tools instead of glusterfs or any other proper solution in my case? I would appreciate it, thanks again!

Regards, Said

On Tue, Nov 12, 2024 at 9:47 AM Pranith Kumar Karampuri < @.***> wrote:

I don't think anyone got glusterfs to work correctly with database to my knowledge.

— Reply to this email directly, view it on GitHub https://github.com/gluster/glusterfs/issues/4430#issuecomment-2469594390, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMWMTT2H4A6M33B2G6JIN7D2AGB4ZAVCNFSM6AAAAABRIDQBO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRZGU4TIMZZGA . You are receiving this because you authored the thread.Message ID: @.***>