exited: unicorn (exit status 1; not expected)

I have followed the quick-start

wget https://raw.githubusercontent.com/sameersbn/docker-gitlab/master/docker-compose.yml
docker-compose up

[root@VM_0_15_centos gitlab]# docker-compose logs
Attaching to gitlab_gitlab_1, gitlab_redis_1, gitlab_postgresql_1
gitlab_1      | Initializing logdir...
gitlab_1      | Initializing datadir...
gitlab_1      | Installing configuration templates...
gitlab_1      | Configuring gitlab...
gitlab_1      | Configuring gitlab::database...Initializing logdir...
gitlab_1      | Initializing datadir...
gitlab_1      | Installing configuration templates...
gitlab_1      | Configuring gitlab...
gitlab_1      | Configuring gitlab::database......
gitlab_1      | Configuring gitlab::redis
gitlab_1      | Configuring gitlab::secrets...
gitlab_1      | Configuring gitlab::sidekiq...
gitlab_1      | Configuring gitlab::gitaly...
gitlab_1      | Configuring gitlab::monitoring...
gitlab_1      | Configuring gitlab::gitlab-workhorse...
gitlab_1      | Configuring gitlab::unicorn...
gitlab_1      | Configuring gitlab::timezone...
gitlab_1      | Configuring gitlab::rack_attack...
gitlab_1      | Configuring gitlab::ci...
gitlab_1      | Configuring gitlab::artifacts...
gitlab_1      | Configuring gitlab::lfs...
gitlab_1      | Configuring gitlab::uploads...
gitlab_1      | Configuring gitlab::mattermost...
gitlab_1      | Configuring gitlab::project_features...
gitlab_1      | Configuring gitlab::oauth...
gitlab_1      | Configuring gitlab::ldap...
gitlab_1      | Configuring gitlab::cron_jobs...
gitlab_1      | Configuring gitlab::backups...
gitlab_1      | Configuring gitlab::backups::schedule...
gitlab_1      | Configuring gitlab::registry...
gitlab_1      | Configuring gitlab::pages...
gitlab_1      | Configuring gitlab-shell...
gitlab_1      | Configuring nginx...
gitlab_1      | Configuring nginx::gitlab...
gitlab_1      | 2018-05-07 21:41:54,407 CRIT Supervisor running as root (no user in config file)
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/gitaly.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,407 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
gitlab_1      | 2018-05-07 21:41:54,431 INFO RPC interface 'supervisor' initialized
gitlab_1      | 2018-05-07 21:41:54,431 CRIT Server 'unix_http_server' running without any HTTP authentication checking
gitlab_1      | 2018-05-07 21:41:54,432 INFO supervisord started with pid 1
gitlab_1      | 2018-05-07 21:41:55,435 INFO spawned: 'gitaly' with pid 595
gitlab_1      | 2018-05-07 21:41:55,440 INFO spawned: 'sidekiq' with pid 596
gitlab_1      | 2018-05-07 21:41:55,447 INFO spawned: 'unicorn' with pid 597
gitlab_1      | 2018-05-07 21:41:55,453 INFO spawned: 'gitlab-workhorse' with pid 598
gitlab_1      | 2018-05-07 21:41:55,454 INFO spawned: 'cron' with pid 599
gitlab_1      | 2018-05-07 21:41:55,456 INFO spawned: 'nginx' with pid 600
gitlab_1      | 2018-05-07 21:41:55,466 INFO spawned: 'sshd' with pid 601
gitlab_1      | 2018-05-07 21:41:56,568 INFO success: gitaly entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:41:56,568 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:41:56,568 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:41:56,568 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:41:56,568 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:41:56,568 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:41:56,568 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:42:37,456 INFO exited: sidekiq (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:42:38,808 INFO spawned: 'sidekiq' with pid 722
gitlab_1      | 2018-05-07 21:42:39,065 INFO exited: unicorn (exit status 1; not expected)
gitlab_1      | 2018-05-07 21:42:40,069 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:42:40,070 INFO spawned: 'unicorn' with pid 725
gitlab_1      | 2018-05-07 21:42:41,076 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:43:17,060 INFO exited: unicorn (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:43:18,241 INFO spawned: 'unicorn' with pid 742
gitlab_1      | 2018-05-07 21:43:19,247 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:43:38,136 INFO exited: sidekiq (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:43:39,327 INFO spawned: 'sidekiq' with pid 747
gitlab_1      | 2018-05-07 21:43:40,328 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:44:14,847 INFO exited: unicorn (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:44:16,276 INFO spawned: 'unicorn' with pid 762
gitlab_1      | 2018-05-07 21:44:17,283 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:44:37,655 INFO exited: sidekiq (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:44:38,826 INFO spawned: 'sidekiq' with pid 769
gitlab_1      | 2018-05-07 21:44:39,828 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:45:13,339 INFO exited: unicorn (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:45:14,529 INFO spawned: 'unicorn' with pid 782
gitlab_1      | 2018-05-07 21:45:15,533 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:45:43,634 INFO exited: sidekiq (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:45:44,687 INFO spawned: 'sidekiq' with pid 793
gitlab_1      | 2018-05-07 21:45:45,689 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:46:14,672 INFO exited: unicorn (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:46:15,954 INFO spawned: 'unicorn' with pid 804
gitlab_1      | 2018-05-07 21:46:16,958 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:46:44,010 INFO exited: sidekiq (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:46:45,083 INFO spawned: 'sidekiq' with pid 815
gitlab_1      | 2018-05-07 21:46:46,085 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:31,371 INFO exited: unicorn (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:47:32,930 INFO spawned: 'unicorn' with pid 828
gitlab_1      | 2018-05-07 21:47:32,931 WARN received SIGTERM indicating exit request
gitlab_1      | 2018-05-07 21:47:32,931 INFO waiting for sshd, gitlab-workhorse, sidekiq, cron, nginx, gitaly, unicorn to die
gitlab_1      | 2018-05-07 21:47:33,313 INFO stopped: sshd (exit status 0)
gitlab_1      | 2018-05-07 21:47:33,595 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:33,595 INFO stopped: nginx (exit status 0)
gitlab_1      | 2018-05-07 21:47:33,596 INFO stopped: cron (terminated by SIGTERM)
gitlab_1      | 2018-05-07 21:47:33,663 INFO stopped: gitlab-workhorse (terminated by SIGTERM)
gitlab_1      | 2018-05-07 21:47:34,734 INFO stopped: unicorn (terminated by SIGQUIT (core dumped))
postgresql_1  | Initializing datadir...
postgresql_1  | Initializing certdir...
postgresql_1  | Initializing logdir...
postgresql_1  | Initializing rundir...
postgresql_1  | Setting resolv.conf ACLs...
postgresql_1  | Creating database user: gitlab
postgresql_1  | Creating database: gitlabhq_production...
postgresql_1  | ‣ Loading pg_trgm extension...
postgresql_1  | ‣ Granting access to gitlab user...
postgresql_1  | Starting PostgreSQL 9.6...
postgresql_1  | LOG:  database system was shut down at 2018-05-07 16:11:40 UTC
postgresql_1  | FATAL:  the database system is starting up
postgresql_1  | Initializing datadir...
postgresql_1  | Initializing certdir...
postgresql_1  | Initializing logdir...
postgresql_1  | Initializing rundir...
postgresql_1  | Setting resolv.conf ACLs...
postgresql_1  | Creating database user: gitlab
postgresql_1  | Creating database: gitlabhq_production...
postgresql_1  | ‣ Loading pg_trgm extension...
postgresql_1  | ‣ Granting access to gitlab user...
postgresql_1  | Starting PostgreSQL 9.6...
postgresql_1  | LOG:  database system was shut down at 2018-05-07 16:11:51 UTC
postgresql_1  | LOG:  MultiXact member wraparound protections are now enabled
postgresql_1  | LOG:  database system is ready to accept connections
postgresql_1  | LOG:  autovacuum launcher started
postgresql_1  | LOG:  received smart shutdown request
postgresql_1  | LOG:  autovacuum launcher shutting down
postgresql_1  | LOG:  shutting down
postgresql_1  | LOG:  database system is shut down
postgresql_1  | Initializing datadir...
postgresql_1  | Initializing certdir...
postgresql_1  | Initializing logdir...
postgresql_1  | Initializing rundir...
postgresql_1  | Setting resolv.conf ACLs...
postgresql_1  | Creating database user: gitlab
postgresql_1  | Creating database: gitlabhq_production...
postgresql_1  | ‣ Loading pg_trgm extension...
postgresql_1  | ‣ Granting access to gitlab user...
postgresql_1  | Starting PostgreSQL 9.6...
postgresql_1  | LOG:  database system was shut down at 2018-05-07 16:17:39 UTC
postgresql_1  | LOG:  MultiXact member wraparound protections are now enabled
postgresql_1  | LOG:  database system is ready to accept connections
postgresql_1  | LOG:  autovacuum launcher started
redis_1       | Starting redis-server...
redis_1       | 1:M 07 May 16:11:37.070 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1       | 1:M 07 May 16:11:37.071 # Server started, Redis version 3.0.6
redis_1       | 1:M 07 May 16:11:37.071 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1       | 1:M 07 May 16:11:37.071 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1       | 1:signal-handler (1525709497) Received SIGTERM scheduling shutdown...
redis_1       | 1:M 07 May 16:11:37.377 # User requested shutdown...
redis_1       | 1:M 07 May 16:11:37.395 # Redis is now ready to exit, bye bye...
redis_1       | Starting redis-server...
redis_1       | 1:M 07 May 16:11:45.673 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1       | 1:M 07 May 16:11:45.673 # Server started, Redis version 3.0.6
redis_1       | 1:M 07 May 16:11:45.673 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1       | 1:M 07 May 16:11:45.673 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1       | 1:signal-handler (1525709852) Received SIGTERM scheduling shutdown...
redis_1       | 1:M 07 May 16:17:32.506 # User requested shutdown...
redis_1       | 1:M 07 May 16:17:33.186 # Redis is now ready to exit, bye bye...
redis_1       | Starting redis-server...
redis_1       | 1:M 07 May 16:17:36.033 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1       | 1:M 07 May 16:17:36.034 # Server started, Redis version 3.0.6
redis_1       | 1:M 07 May 16:17:36.034 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1       | 1:M 07 May 16:17:36.034 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
gitlab_1      | 2018-05-07 21:47:35,062 INFO stopped: sidekiq (terminated by SIGTERM)
gitlab_1      | 2018-05-07 21:47:35,356 INFO stopped: gitaly (exit status 1)
gitlab_1      | Initializing logdir...
gitlab_1      | Initializing datadir...
gitlab_1      | Installing configuration templates...
gitlab_1      | Configuring gitlab...
gitlab_1      | Configuring gitlab::database....
gitlab_1      | Configuring gitlab::redis
gitlab_1      | Configuring gitlab::secrets...
gitlab_1      | Configuring gitlab::sidekiq...
gitlab_1      | Configuring gitlab::gitaly...
gitlab_1      | Configuring gitlab::monitoring...
gitlab_1      | Configuring gitlab::gitlab-workhorse...
gitlab_1      | Configuring gitlab::unicorn...
gitlab_1      | Configuring gitlab::timezone...
gitlab_1      | Configuring gitlab::rack_attack...
gitlab_1      | Configuring gitlab::ci...
gitlab_1      | Configuring gitlab::artifacts...
gitlab_1      | Configuring gitlab::lfs...
gitlab_1      | Configuring gitlab::uploads...
gitlab_1      | Configuring gitlab::mattermost...
gitlab_1      | Configuring gitlab::project_features...
gitlab_1      | Configuring gitlab::oauth...
gitlab_1      | Configuring gitlab::ldap...
gitlab_1      | Configuring gitlab::cron_jobs...
gitlab_1      | Configuring gitlab::backups...
gitlab_1      | Configuring gitlab::registry...
gitlab_1      | Configuring gitlab::pages...
gitlab_1      | Configuring gitlab-shell...
gitlab_1      | Configuring nginx...
gitlab_1      | Configuring nginx::gitlab...
gitlab_1      | 2018-05-07 21:47:43,259 CRIT Supervisor running as root (no user in config file)
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/gitaly.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,259 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
gitlab_1      | 2018-05-07 21:47:43,310 INFO RPC interface 'supervisor' initialized
gitlab_1      | 2018-05-07 21:47:43,310 CRIT Server 'unix_http_server' running without any HTTP authentication checking
gitlab_1      | 2018-05-07 21:47:43,310 INFO supervisord started with pid 1
gitlab_1      | 2018-05-07 21:47:44,312 INFO spawned: 'gitaly' with pid 581
gitlab_1      | 2018-05-07 21:47:44,314 INFO spawned: 'sidekiq' with pid 582
gitlab_1      | 2018-05-07 21:47:44,316 INFO spawned: 'unicorn' with pid 583
gitlab_1      | 2018-05-07 21:47:44,317 INFO spawned: 'gitlab-workhorse' with pid 584
gitlab_1      | 2018-05-07 21:47:44,319 INFO spawned: 'cron' with pid 585
gitlab_1      | 2018-05-07 21:47:44,328 INFO spawned: 'nginx' with pid 586
gitlab_1      | 2018-05-07 21:47:44,330 INFO spawned: 'sshd' with pid 587
gitlab_1      | 2018-05-07 21:47:45,579 INFO success: gitaly entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:45,579 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:45,579 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:45,579 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:45,579 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:45,579 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:47:45,579 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:48:34,980 INFO exited: sidekiq (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:48:36,072 INFO spawned: 'sidekiq' with pid 710
gitlab_1      | 2018-05-07 21:48:36,309 INFO exited: unicorn (exit status 1; not expected)
gitlab_1      | 2018-05-07 21:48:37,313 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:48:37,315 INFO spawned: 'unicorn' with pid 713
gitlab_1      | 2018-05-07 21:48:38,319 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:49:20,777 INFO exited: unicorn (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:49:21,815 INFO spawned: 'unicorn' with pid 730
gitlab_1      | 2018-05-07 21:49:22,818 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
gitlab_1      | 2018-05-07 21:49:45,125 INFO exited: sidekiq (terminated by SIGKILL; not expected)
gitlab_1      | 2018-05-07 21:49:46,436 INFO spawned: 'sidekiq' with pid 735
gitlab_1      | 2018-05-07 21:49:47,438 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Start by reproducing the quick-start commands from docker-compose.yml and collect the complete output from docker-compose logs. Investigate the repeated unicorn and sidekiq exits alongside the PostgreSQL startup messages. Done means the cause of the container startup failure is identified and a verified resolution or required configuration is documented.