1. casa
  2. Domanda e risposta
  3. Esecuzione Gitlab Docker

Esecuzione Gitlab Docker

2016-02-22 15 views
8

Sto seguendo queste istruzioni: http://doc.gitlab.com/omnibus/dockerEsecuzione Gitlab Docker

Tuttavia http://localhost è dice Webpage is not available.

Qui ci sono i comandi che sto correndo (Ubuntu 14.04 LTS):

[email protected]:~$ docker version 
    Client: 
    Version:  1.9.1 
    API version: 1.21 
    Go version: go1.4.3 
    Git commit: a34a1d5 
    Built:  Fri Nov 20 17:56:04 UTC 2015 
    OS/Arch:  linux/amd64 

    Server: 
    Version:  1.9.1 
    API version: 1.21 
    Go version: go1.4.3 
    Git commit: a34a1d5 
    Built:  Fri Nov 20 17:56:04 UTC 2015 
    OS/Arch:  linux/amd64 

    [email protected]:~$ sudo docker run --detach \ 
    >  --hostname gitlab.example.com \ 
    >  --publish 443:443 --publish 80:80 --publish 22:22 \ 
    >  --name gitlab \ 
    >  --restart always \ 
    >  --volume /srv/gitlab/config:/etc/gitlab \ 
    >  --volume /srv/gitlab/logs:/var/log/gitlab \ 
    >  --volume /srv/gitlab/data:/var/opt/gitlab \ 
    >  gitlab/gitlab-ce:latest 
    613d4d2d612f977d3d25746a169d9209acb864e57c5184083dccd02b1e4a157c 

    [email protected]:~$ docker ps 
    CONTAINER ID  IMAGE      COMMAND    CREATED    STATUS    PORTS               NAMES 
    613d4d2d612f  gitlab/gitlab-ce:latest "/assets/wrapper" 4 seconds ago  Up 2 seconds  0.0.0.0:22->22/tcp, 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp gitlab

Se rieseguire docker ps ottengo questo:

CONTAINER ID  IMAGE      COMMAND    CREATED    STATUS        PORTS               NAMES 
    613d4d2d612f  gitlab/gitlab-ce:latest "/assets/wrapper" 9 minutes ago  Restarting (1) About a minute ago 0.0.0.0:22->22/tcp, 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp gitlab

Dice Restarting about a minute ago... ... vuol dire c'è qualcosa che non va internamente?

[EDIT - AGGIUNTA DI TRONCHI]

[email protected]:~$ sudo mkdir -p /var/log/gitlab/reconfigure 

    [email protected]:~$ sudo docker run --detach \ 
    >  --hostname gitlab.example.com \ 
    >  --publish 443:443 --publish 80:80 --publish 22:22 \ 
    >  --name gitlab \ 
    >  --restart always \ 
    >  --volume /srv/gitlab/config:/etc/gitlab \ 
    >  --volume /srv/gitlab/logs:/var/log/gitlab \ 
    >  --volume /srv/gitlab/data:/var/opt/gitlab \ 
    >  gitlab/gitlab-ce:latest 
    f4dee0a603bdc95594e8a77d51762f2d78d44ec077f2d57645e651ed628a4d6b 

    [email protected]:~$ docker logs 
    docker: "logs" requires 1 argument. 
    See 'docker logs --help'. 

    Usage: docker logs [OPTIONS] CONTAINER 

    Fetch the logs of a container 

    [email protected]:~$ docker logs gitlab 
    Thank you for using GitLab Docker Image! 
    Current version: gitlab-ce=8.5.0-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... 
    /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 
    [2016-02-23T01:16:47+00:00] FATAL: Failed to open or create log file at /var/log/gitlab/reconfigure/1456190207.log: Errno::ENOENT (No such file or directory @ rb_sysopen - /var/log/gitlab/reconfigure/1456190207.log) 
    [2016-02-23T01:16:47+00:00] FATAL: Aborting due to invalid 'log_location' configuration 
    Thank you for using GitLab Docker Image! 
    Current version: gitlab-ce=8.5.0-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... 
    /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 
    [2016-02-23T01:16:51+00:00] FATAL: Failed to open or create log file at /var/log/gitlab/reconfigure/1456190211.log: Errno::ENOENT (No such file or directory @ rb_sysopen - /var/log/gitlab/reconfigure/1456190211.log) 
    [2016-02-23T01:16:51+00:00] FATAL: Aborting due to invalid 'log_location' configuration 
    Thank you for using GitLab Docker Image! 
    Current version: gitlab-ce=8.5.0-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... 
    /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 
    [2016-02-23T01:16:56+00:00] FATAL: Failed to open or create log file at /var/log/gitlab/reconfigure/1456190216.log: Errno::ENOENT (No such file or directory @ rb_sysopen - /var/log/gitlab/reconfigure/1456190216.log) 
    [2016-02-23T01:16:56+00:00] FATAL: Aborting due to invalid 'log_location' configuration 
    Thank you for using GitLab Docker Image! 
    Current version: gitlab-ce=8.5.0-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... 
    /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 
    [2016-02-23T01:17:02+00:00] FATAL: Failed to open or create log file at /var/log/gitlab/reconfigure/1456190222.log: Errno::ENOENT (No such file or directory @ rb_sysopen - /var/log/gitlab/reconfigure/1456190222.log) 
    [2016-02-23T01:17:02+00:00] FATAL: Aborting due to invalid 'log_location' configuration 
    Thank you for using GitLab Docker Image! 
    Current version: gitlab-ce=8.5.0-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 


    [email protected]:~$ docker ps 
    CONTAINER ID  IMAGE      COMMAND    CREATED    STATUS       PORTS               NAMES 
    f4dee0a603bd  gitlab/gitlab-ce:latest "/assets/wrapper" 39 seconds ago  Restarting (1) 4 seconds ago 0.0.0.0:22->22/tcp, 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp gitlab

E ancora non si avvia, anche dopo la creazione /var/log/gitlab/reconfigure manualmente.

fonte

2016-02-22 Ole

+0

Non so cosa sta succedendo. Ma, per favore, fornisci l'output di 'logger logs gitlab'. Qui possiamo vedere se qualcosa è andato storto durante l'avvio di gitlab. –

+0

quindi cosa si ottiene da 'registri docker 613d4d2d612f' – BMW

risposta

6

Modifica il comando finestra mobile al seguente risolto il problema per me:

sudo docker run -i \ 
    --hostname ubuntu \ 
    --publish 443:443 --publish 80:80 --publish 2222:22 \ 
    --name gitlab \ 
    --restart always \ 
    --volume /srv/gitlab/config:/etc/gitlab \ 
    --volume /srv/gitlab/logs:/var/log/gitlab \ 
    --volume /srv/gitlab/data:/var/opt/gitlab \ 
    --volume /srv/gitlab/logs/reconfigure:/var/log/gitlab/reconfigure \ 
    gitlab/gitlab-ce:latest

Nota che ho usato -i così ho potuto guardarlo start up, ma è possibile impostare di nuovo a --detach.

fonte

2016-02-23 04:14:52

+0

Questo ha fatto il trucco - Grazie! – Ole

+2

Non è necessario modificare il comando. Anche la creazione manuale della directory ha funzionato. Vedi http://stackoverflow.com/a/35566517/2966331 –

6

Ho avuto questo problema e l'ho risolto creando una cartella che mancava. Dovrebbero essere stati fatti dagli script stessi.

/srv/gitlab/logs/reconfigure

fonte

2016-02-23 00:19:01 eyecreate

+0

sì, funziona. In realtà è come aggiungere una mappatura del volume come: --volume/srv/gitlab/logs/reconfigure:/var/log/gitlab/riconfigura – Bright

+1

Non ho fortuna per me qui. Gitlab ha già creato tale cartella sull'host e sta eseguendo 'docker exec -it gitlab update-permissions' segnala che non è possibile trovare un numero di file per i quali non è chiaro il motivo per cui non è in grado di crearli se ha già creato molte altre cartelle e file già in quelle cartelle montate su contenitori. –

1

fare quello che dice il registro:

docker exec -it gitlab update-permissions 
docker restart gitlab

fonte

2016-04-29 08:21:21 thSoft

0

Non utilizza l'ultimo immagine gitlab/gitlab-ce:latest ha lavorato per me.

Ma gitlab/gitlab-ce:9.5.4-ce.0 ha funzionato per me.

Ho lottato con lo stesso problema. Continuò a riavviarsi. I registri in cui si parla di permessi sui file e anche di compilare errori.

Qui è la mia impostazione di partenza:

#sudo docker run -i \ 
sudo docker run --detach \ 
    --env GITLAB_OMNIBUS_CONFIG="external_url 'http://192.168.56.101/'; gitlab_rails['lfs_enabled'] = true;" \ 
    --hostname ubse-gitlab \ 
    --publish 443:443 --publish 80:80 --publish 23:22 \ 
    --name gitlab \ 
    --restart always \ 
    --volume /srv/gitlab/config:/etc/gitlab \ 
    --volume /srv/gitlab/logs:/var/log/gitlab \ 
    --volume /srv/gitlab/data:/var/opt/gitlab \ 
    --volume /srv/gitlab/logs/reconfigure:/var/log/gitlab/reconfigure \ 
    gitlab/gitlab-ce:9.5.4-ce.0

fonte

2017-09-17 06:29:36

Problemi correlati

 Problemi correlati