------ Summary MacOS High Sierra, Docker for Mac latest version Running gitlab using docker works but starting the same container using a docker-compose file does not ! gitlab | ==> /var/log/gitlab/unicorn/current <== gitlab | 2018-02-23_08:35:09.18083 master failed to start, check stderr log for details gitlab | gitlab | ==> /var/log/gitlab/unicorn/unicorn_stdout.log <== gitlab | bundler: failed to load command: unicorn (/opt/gitlab/embedded/bin/unicorn) gitlab | fails to start and then I get a 502 error when accessing the web interface. ### Steps to reproduce Starting Gitlab-CE using the command line works. "docker run --hostname localhost --publish 443:443 --publish 80:80 --publish 22:22 --name gitlab --restart always --volume config:/etc/gitlab --volume logs:/var/log/gitlab --volume data:/var/opt/gitlab gitlab/gitlab-ce:latest" Doing exactly the same using docker compose does not: version: '2' services: gitlab: image: gitlab/gitlab-ce:rc container_name: "gitlab" restart: always hostname: 'localhost' environment: GITLAB_OMNIBUS_CONFIG: | external_url 'http://localhost' unicorn['worker_timeout'] = 120 unicorn['worker_processes'] = 2 ports: - 80:80 - 443:443 - 22:22 networks: - front-tier volumes: - ./gitlab/config:/etc/gitlab - ./gitlab/logs:/var/log/gitlab - ./gitlab/data:/var/opt/gitlab networks: front-tier: driver: bridge Running Gitlab using the above file produces the error mentioned above. And gives a 502 error when connecting to the web service on port 80.