solidnerd
commented
7 years ago It's running on 10080 .
Am 09.05.2017 16:48 schrieb "geoff golder" notifications@github.com:
I am using Docker Community Edition on OSX
Version 17.03.1-ce-mac5 (16048) Channel: stable b18e2a50cc
I am not sure if this is still using a VM? I have tested a 'hello-world' example here: https://github.com/crccheck/docker-hello-world
And this allows me to see the served HTML at localhost:80
When I use the docker-compose.yml (only adjustments being the 3 secret keys being added), I don't seem to get any errors:
~/src/gitlabdocker geoff$ sudo docker-compose up Starting gitlabdocker_postgresql_1 Starting gitlabdocker_redis_1 Recreating gitlabdocker_gitlab_1 Attaching to gitlabdocker_postgresql_1, gitlabdocker_redis_1, gitlabdocker_gitlab_1 postgresql_1 | Initializing datadir... redis_1 | Starting redis-server... redis_1 | [1] 09 May 14:36:56.064 # Server started, Redis version 2.8.4 gitlab_1 | Initializing logdir... gitlab_1 | Initializing datadir... gitlab_1 | Installing configuration templates... gitlab_1 | Configuring gitlab... 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 2017-05-09 14:37:08 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 gitlab_1 | Configuring gitlab::database............. gitlab_1 | Configuring gitlab::redis gitlab_1 | Configuring gitlab::secrets... gitlab_1 | Configuring gitlab::sidekiq... 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::mattermost... gitlab_1 | Configuring gitlab::project_features... gitlab_1 | Configuring gitlab::oauth... gitlab_1 | Configuring gitlab::ldap... 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 | 2017-05-09 20:07:11,091 CRIT Supervisor running as root (no user in config file) gitlab_1 | 2017-05-09 20:07:11,091 WARN Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing gitlab_1 | 2017-05-09 20:07:11,091 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing gitlab_1 | 2017-05-09 20:07:11,091 WARN Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing gitlab_1 | 2017-05-09 20:07:11,091 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing gitlab_1 | 2017-05-09 20:07:11,091 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing gitlab_1 | 2017-05-09 20:07:11,091 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing gitlab_1 | 2017-05-09 20:07:11,091 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing gitlab_1 | 2017-05-09 20:07:11,107 INFO RPC interface 'supervisor' initialized gitlab_1 | 2017-05-09 20:07:11,107 CRIT Server 'unix_http_server' running without any HTTP authentication checking gitlab_1 | 2017-05-09 20:07:11,107 INFO supervisord started with pid 1 gitlab_1 | 2017-05-09 20:07:12,113 INFO spawned: 'sidekiq' with pid 531 gitlab_1 | 2017-05-09 20:07:12,115 INFO spawned: 'unicorn' with pid 532 gitlab_1 | 2017-05-09 20:07:12,117 INFO spawned: 'gitlab-workhorse' with pid 533 gitlab_1 | 2017-05-09 20:07:12,119 INFO spawned: 'cron' with pid 534 gitlab_1 | 2017-05-09 20:07:12,121 INFO spawned: 'nginx' with pid 535 gitlab_1 | 2017-05-09 20:07:12,122 INFO spawned: 'sshd' with pid 540 gitlab_1 | 2017-05-09 20:07:13,766 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) gitlab_1 | 2017-05-09 20:07:13,766 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) gitlab_1 | 2017-05-09 20:07:13,766 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) gitlab_1 | 2017-05-09 20:07:13,767 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) gitlab_1 | 2017-05-09 20:07:13,767 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) gitlab_1 | 2017-05-09 20:07:13,767 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) gitlab_1 | 2017-05-09 20:07:23,152 INFO exited: unicorn (exit status 1; not expected) gitlab_1 | 2017-05-09 20:07:24,156 INFO spawned: 'unicorn' with pid 558 gitlab_1 | 2017-05-09 20:07:25,776 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
However all attempts to reach localhost:80 now are just refused.
~ geoff$ sudo docker ps Password: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES b8fe389b92d0 sameersbn/gitlab:9.1.2 "/sbin/entrypoint...." 7 minutes ago Up 7 minutes 443/tcp, 0.0.0.0:10022->22/tcp, 0.0.0.0:10080->80/tcp gitlabdocker_gitlab_1 a054c27c5c07 sameersbn/postgresql:9.6-2 "/sbin/entrypoint.sh" 22 minutes ago Up 7 minutes 5432/tcp gitlabdocker_postgresql_1 f87530b91d8e sameersbn/redis:latest "/sbin/entrypoint...." 22 minutes ago Up 7 minutes 6379/tcp gitlabdocker_redis_1 ~ geoff$
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sameersbn/docker-gitlab/issues/1206, or mute the thread https://github.com/notifications/unsubscribe-auth/AA2GbzpxgR27C3LFogLN020pMJD7jXZjks5r4HyggaJpZM4NVbXf .
gdoteof
I am using Docker Community Edition on OSX
Version 17.03.1-ce-mac5 (16048) Channel: stable b18e2a50cc
I am not sure if this is still using a VM? I have tested a 'hello-world' example here: https://github.com/crccheck/docker-hello-world
And this allows me to see the served HTML at localhost:80
When I use the docker-compose.yml (only adjustments being the 3 secret keys being added), I don't seem to get any errors:
However all attempts to reach localhost:80 now are just refused.