Skip to content

Current Omnibus GitLab containers for both CE and EE do not work on Apple M1 max mac

Summary

The installation gets stuck at/during rails_migration step:

Recipe: gitlab::database_migrations[0m
  * ruby_block[check remote PG version] action nothing (skipped due to action :nothing)
  * rails_migration[gitlab-rails] action run

Steps to reproduce

Perform the following, on a Apple Macbook with an M1 processor (arm64)

docker run --detach --hostname localhost \
   --publish 80:80 \
   --name gitlab \
   --restart always \
   --volume ~/ee_volume/config:/etc/gitlab \
   --volume ~/ee_volume/logs:/var/log/gitlab \
   --volume ~/ee_volume/data:/var/opt/gitlab \
   --shm-size 256m \
   gitlab/gitlab-ce:latest

What is the current bug behavior?

A healthy gitlab instance is NOT spun up

What is the expected correct behavior?

A healthy gitlab instance should be installed

Relevant logs

Attaching docker logs m1_container_logs.log

Details of package version

gitlab-ce:latest and gitlab-ee:latest as of 2022-01-31

Environment details

  • Operating System: macOS Monterey

  • Installation Target, remove incorrect values:

    • Other: Apple M1 max
  • Installation Type, remove incorrect values:

    • New Installation
  • Is there any other software running on the machine: No other version of gitlab running

  • Is this a single or multiple node installation?

  • Resources

    • CPU: 10
    • Memory total: 32GB

/edit: added clarity & specific dates for latest

Edited by Jason Plum