Question

我正在运行Openshift原点，各种项目模板似乎工作正常，除了gitlab。当重新启动机器或尝试重新启动gitlab-ce pod时，它似乎要么花费很长时间（不到10米），要么因超时而失败。似乎总是将卡住放在同一个地方。

如何解决此部署问题？

Thank you for using GitLab Docker Image!
Current version: gitlab-ce=8.14.1-ce.1

Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:

  docker exec -it gitlab vim /etc/gitlab/gitlab.rb
  docker restart gitlab

For a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md

If this container fails to start due to permission problems try to fix it by executing:

  docker exec -it gitlab update-permissions
  docker restart gitlab

Preparing services...
Starting services...
Configuring GitLab package...
/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
Configuring GitLab...


  * Moving existing certificates found in /opt/gitlab/embedded/ssl/certs

  * Symlinking existing certificates found in /etc/gitlab/trusted-certs

Answer 1

您的流程会在https://hub.docker.com/r/gitlab/gitlab-ce/~/dockerfile/

上挂起

wrapper

线

您可以通过执行

手动运行它

docker run -it gitlab/gitlab-ce 'bash'

并进入wrapper

如果你设法看到

Starting Chef...

那之后的一切都应该没问题。

Answer 2

这对我来说根本原因，结果是缺乏记忆。我正在运行AWS EC2 t1.micro - 1GB。为了解决这个问题，我停止了EC2实例并升级到了t2.small（2GB）。我再次启动了EC2，运行free检查内存是否可用，然后再次运行docker run -ti gitlab/gitlab-ce命令。

此外，这样可以节省我几次，以清除损坏的码头工具状态：

service docker stop sudo rm -rf /var/run/docker sudo rm /var/run/docker.* service docker start

关于OpenShift Origin的Gitlab卡在＆＃34; Symlinking / etc / gitlab / trusted-certs＆＃34;

2 个答案: