- I am running a Synology 412+ with DSM 6.1.4-15217 Update 5
- I installed Docker and GitLab from the package manager.
- I then, incorrectly so, installed GitLab again (atop/parallel with the package manger install) from here https://hub.docker.com/r/sameersbn/gitlab/#prerequisites thinking I was getting the latest version than what Synology made available. This actually worked albeit painfully slow.
- I uninstalled all the above, Docker, GitLab, MariaDB, etc… and started over with only the Synology package.
I would like to mention that this was my first exposure to Docker and containers as well as any Git/GitLab admin so I am still learning about them thus I claim to understand very little at the moment.
After the fresh install I get the “502 too much time to respond” error. When I log on to the GitLab container and run
tail -f /var/log/gitlab/gitlab/unicorn.stderr.log
It outputs the following:
from /home/git/gitlab/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/bin/unicorn_rails:209:in `<top (required)>' from /home/git/gitlab/vendor/bundle/ruby/2.3.0/bin/unicorn_rails:22:in `load' from /home/git/gitlab/vendor/bundle/ruby/2.3.0/bin/unicorn_rails:22:in `<main>' I, [2018-01-12T15:33:58.477934 #976] INFO -- : Refreshing Gem list I, [2018-01-12T15:40:18.963037 #976] INFO -- : listening on addr=/home/git/gitlab/tmp/sockets/gitlab.socket fd=22 I, [2018-01-12T15:40:29.326164 #976] INFO -- : listening on addr=127.0.0.1:8080 fd=25 I, [2018-01-12T15:40:36.106423 #976] INFO -- : master process ready I, [2018-01-12T15:40:36.523794 #991] INFO -- : worker=0 ready I, [2018-01-12T15:40:36.523793 #994] INFO -- : worker=1 ready I, [2018-01-12T15:40:36.524014 #997] INFO -- : worker=2 ready
Any guidance would be highly appreciated.