Hello,
I’m trying to update my Gitlab installation. It’s from the time Gitlab didn’t have its own Docker images and only a guide how to self build the image was available. According to the guide, I created two containers, gitlab_data and gitlab_app.
I’m trying to pull new Docker image and use the existing data and configuration, however Gitlab fails to start after the container is initialized, giving permission denied and read-only filesystem errors, mostly on sockets.
The command I’m starting the container is:
$ sudo docker run --detach --publish 8081:80 --publish 8080:443 --publish 2222:22 --name gitlab --restart always --volumes-from gitlab_data gitlab/gitlab-ce:latest
The errors I’m getting:
$ sudo docker logs gitlab
/opt/gitlab/embedded/bin/runsvdir-start: line 24: ulimit: pending signals: cannot modify limit: Operation not permitted
/opt/gitlab/embedded/bin/runsvdir-start: line 34: ulimit: max user processes: cannot modify limit: Operation not permitted
/opt/gitlab/embedded/bin/runsvdir-start: line 37: /proc/sys/fs/file-max: Read-only file system
... (further down in the log)
==> /var/log/gitlab/unicorn/current <==
2015-07-28_22:20:48.03510 failed to start a new unicorn master
2015-07-28_22:20:48.04695 starting new unicorn master
2015-07-28_22:20:48.99869 /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:732:in `initialize': Permission denied @ rb_sysopen - /var/log/gitlab/unicorn/unicorn_stderr.log (Errno::EACCES)
2015-07-28_22:20:49.00031 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:732:in `open'
2015-07-28_22:20:49.00043 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:732:in `redirect_io'
2015-07-28_22:20:49.00069 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:177:in `stderr_path='
2015-07-28_22:20:49.00076 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/configurator.rb:111:in `block in commit!'
2015-07-28_22:20:49.00085 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/configurator.rb:108:in `each'
2015-07-28_22:20:49.00094 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/configurator.rb:108:in `commit!'
2015-07-28_22:20:49.00103 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/lib/unicorn/http_server.rb:121:in `initialize'
2015-07-28_22:20:49.00111 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/bin/unicorn:126:in `new'
2015-07-28_22:20:49.00125 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/gems/unicorn-4.6.3/bin/unicorn:126:in `<top (required)>'
2015-07-28_22:20:49.00133 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/bin/unicorn:23:in `load'
2015-07-28_22:20:49.00141 from /opt/gitlab/embedded/service/gem/ruby/2.1.0/bin/unicorn:23:in `<main>'
2015-07-28_22:20:49.02401 master failed to start, check stderr log for details
2015-07-28_22:20:50.03102 failed to start a new unicorn master
I’m quite lost here. I already tried to check permissions in the data container and copying the files off it (and starting the container with --volume /srv/gitlab/... params). The other components seem to work well, nginx displays Gitlab’s 502 themed page. If I start a container without connecting existing data, Gitlab works fine, as expected.
Thanks for any help.