Docker-gitlab: GitLab 10.4.2 on Synology DS412+

[edtriccorp]

Hello,

I am attempting to install GitLab 10.4.2 docker image on Synology DS412+ that has been upgraded to 4GB and is running "DSM 6.1.4-15217 Update 5". I am using the official Synology Docker install from the package center. I have not found a way to install the latest Docker on the DS412+ as of yet. When running docker-compose -f docker-compose..yml up I get:

postgresql_1 | WARNING: no logs are available with the 'db' log driver
redis_1 | WARNING: no logs are available with the 'db' log driver
gitlab_1 | WARNING: no logs are available with the 'db' log driver
docker_gitlab_1 exited with code 1

Details:

Output of: docker version

Client:
 Version:      17.05.0-ce
 API version:  1.29
 Go version:   go1.8
 Git commit:   9f07f0e-synology
 Built:        Fri Dec 15 19:37:44 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.05.0-ce
 API version:  1.29 (minimum version 1.12)
 Go version:   go1.8
 Git commit:   9f07f0e-synology
 Built:        Fri Dec 15 19:37:44 2017
 OS/Arch:      linux/amd64
 Experimental: false"

Output of: docker info 

Containers: 3
 Running: 0
 Paused: 0
 Stopped: 3
Images: 3
Server Version: 17.05.0-ce
Storage Driver: aufs
 Root Dir: /volume1/@docker/aufs
 Backing Filesystem: extfs
 Dirs: 31
 Dirperm1 Supported: true
Logging Driver: db
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: fd189da3e13a3ef3d6d9eb73c5cd4697b4536cdd (expected: 9048e5e50717ea4497b757314bad98ea3763c145)
runc version: a2d6e07aab95ff37fb63cf5dec3c40d29940194f (expected: 9c2d8d184e5da67c95d601382adf14862e4f2228)
init version: 7a83305 (expected: 949e6fa)
Security Options:
 apparmor
Kernel Version: 3.10.102
Operating System: <unknown>
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.855GiB
Name: mystation
ID: GJFX:U4TY:A2YU:ALP4:QIDM:GVDB:4EJD:QND5:EQG6:T6EN:NQAU:MEM6
Docker Root Dir: /volume1/@docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No kernel memory limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

Output of: sudo docker-compose -f docker-compose.yml up

Creating network "docker_default" with the default driver
Starting docker_postgresql_1 ...
Starting docker_redis_1 ...
Starting docker_redis_1
Starting docker_redis_1 ... done
Starting docker_gitlab_1 ...
Starting docker_gitlab_1 ... done
Attaching to docker_postgresql_1, docker_redis_1, docker_gitlab_1
postgresql_1  | WARNING: no logs are available with the 'db' log driver
redis_1       | WARNING: no logs are available with the 'db' log driver
gitlab_1      | WARNING: no logs are available with the 'db' log driver
docker_gitlab_1 exited with code 1
gitlab_1      | WARNING: no logs are available with the 'db' log driver
docker_gitlab_1 exited with code 1
gitlab_1      | WARNING: no logs are available with the 'db' log driver
docker_gitlab_1 exited with code 1
gitlab_1      | WARNING: no logs are available with the 'db' log driver
docker_gitlab_1 exited with code 1
gitlab_1      | WARNING: no logs are available with the 'db' log driver
docker_gitlab_1 exited with code 1
gitlab_1      | WARNING: no logs are available with the 'db' log driver
docker_gitlab_1 exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Killing docker_gitlab_1 ... done
Killing docker_redis_1 ... done
Killing docker_postgresql_1 ... done

My docker-compose.yml (with sensitive info removed) 

version: '2'

services:
  redis:
    restart: always
    image: sameersbn/redis:latest
    command:
    - --loglevel warning
    volumes:
    - /volume1/docker/gitlab/redis:/var/lib/redis:Z

  postgresql:
    restart: always
    image: sameersbn/postgresql:9.6-2
    volumes:
    - /volume1/docker/gitlab/postgresql:/var/lib/postgresql:Z
    environment:
    - DB_USER=gitlab
    - DB_PASS=mypassword
    - DB_NAME=gitlabhq_production
    - DB_EXTENSION=pg_trgm

  gitlab:
    restart: always
    image: sameersbn/gitlab:10.4.2
    depends_on:
    - redis
    - postgresql
    ports:
    - "10080:80"
    - "10022:22"
    volumes:
    - /volume1/docker/gitlab/gitlab:/home/git/data:Z
    environment:
    - DEBUG=true

    - DB_ADAPTER=postgresql
    - DB_HOST=postgresql
    - DB_PORT=5432
    - DB_USER=gitlab
    - DB_PASS=mypassword
    - DB_NAME=gitlabhq_production

    - REDIS_HOST=redis
    - REDIS_PORT=6379

    - TZ=America/Los_Angeles
    - GITLAB_TIMEZONE=America/Los_Angeles

    - GITLAB_HTTPS=true
    - SSL_SELF_SIGNED=false

    - GITLAB_HOST=my.synology.me
    - GITLAB_PORT=10080
    - GITLAB_SSH_PORT=10022
    - GITLAB_RELATIVE_URL_ROOT=
    - GITLAB_SECRETS_DB_KEY_BASE=keybase1
    - GITLAB_SECRETS_SECRET_KEY_BASE=keybase2
    - GITLAB_SECRETS_OTP_KEY_BASE=keybase3

    - GITLAB_ROOT_PASSWORD=mypassword
    - GITLAB_ROOT_EMAIL=myemail@mydomain

    - GITLAB_NOTIFY_ON_BROKEN_BUILDS=true
    - GITLAB_NOTIFY_PUSHER=false

    - GITLAB_EMAIL=myemail@mydomain
    - GITLAB_EMAIL_REPLY_TO=myemail@mydomain
    - GITLAB_INCOMING_EMAIL_ADDRESS=myemail@mydomain

    - GITLAB_BACKUP_SCHEDULE=daily
    - GITLAB_BACKUP_TIME=01:00

    - SMTP_ENABLED=true
    - SMTP_DOMAIN=www.mydomain.com
    - SMTP_HOST=smtp.myhost.net
    - SMTP_PORT=587
    - SMTP_USER=myemail@mydomain
    - SMTP_PASS=mypassword
    - SMTP_STARTTLS=true
    - SMTP_AUTHENTICATION=login

    - IMAP_ENABLED=true
    - IMAP_HOST=imap.myhost.net
    - IMAP_PORT=993
    - IMAP_USER=myemail@mydomain
    - IMAP_PASS=mypassword
    - IMAP_SSL=true
    - IMAP_STARTTLS=false

    - OAUTH_ENABLED=false
    - OAUTH_AUTO_SIGN_IN_WITH_PROVIDER=
    - OAUTH_ALLOW_SSO=
    - OAUTH_BLOCK_AUTO_CREATED_USERS=true
    - OAUTH_AUTO_LINK_LDAP_USER=false
    - OAUTH_AUTO_LINK_SAML_USER=false
    - OAUTH_EXTERNAL_PROVIDERS=

    - OAUTH_CAS3_LABEL=cas3
    - OAUTH_CAS3_SERVER=
    - OAUTH_CAS3_DISABLE_SSL_VERIFICATION=false
    - OAUTH_CAS3_LOGIN_URL=/cas/login
    - OAUTH_CAS3_VALIDATE_URL=/cas/p3/serviceValidate
    - OAUTH_CAS3_LOGOUT_URL=/cas/logout

    - OAUTH_GOOGLE_API_KEY=
    - OAUTH_GOOGLE_APP_SECRET=
    - OAUTH_GOOGLE_RESTRICT_DOMAIN=

    - OAUTH_FACEBOOK_API_KEY=
    - OAUTH_FACEBOOK_APP_SECRET=

    - OAUTH_TWITTER_API_KEY=
    - OAUTH_TWITTER_APP_SECRET=

    - OAUTH_GITHUB_API_KEY=
    - OAUTH_GITHUB_APP_SECRET=
    - OAUTH_GITHUB_URL=
    - OAUTH_GITHUB_VERIFY_SSL=

   - OAUTH_GITLAB_API_KEY=
    - OAUTH_GITLAB_APP_SECRET=

    - OAUTH_BITBUCKET_API_KEY=
    - OAUTH_BITBUCKET_APP_SECRET=

    - OAUTH_SAML_ASSERTION_CONSUMER_SERVICE_URL=
    - OAUTH_SAML_IDP_CERT_FINGERPRINT=
    - OAUTH_SAML_IDP_SSO_TARGET_URL=
    - OAUTH_SAML_ISSUER=
    - OAUTH_SAML_LABEL="Our SAML Provider"
    - OAUTH_SAML_NAME_IDENTIFIER_FORMAT=urn:oasis:names:tc:SAML:2.0:nameid-format:transient
    - OAUTH_SAML_GROUPS_ATTRIBUTE=
    - OAUTH_SAML_EXTERNAL_GROUPS=
    - OAUTH_SAML_ATTRIBUTE_STATEMENTS_EMAIL=
    - OAUTH_SAML_ATTRIBUTE_STATEMENTS_NAME=
    - OAUTH_SAML_ATTRIBUTE_STATEMENTS_FIRST_NAME=
    - OAUTH_SAML_ATTRIBUTE_STATEMENTS_LAST_NAME=

    - OAUTH_CROWD_SERVER_URL=
    - OAUTH_CROWD_APP_NAME=
    - OAUTH_CROWD_APP_PASSWORD=

    - OAUTH_AUTH0_CLIENT_ID=
    - OAUTH_AUTH0_CLIENT_SECRET=
    - OAUTH_AUTH0_DOMAIN=

    - OAUTH_AZURE_API_KEY=
    - OAUTH_AZURE_API_SECRET=
    - OAUTH_AZURE_TENANT_ID=

[mikeblanton]

I’m running it on a 415+ with no issues. I get the db error as well, but that doesn’t seem to be impacting it at all. Given that the gitlab docker is exiting over and over with a -1, you’re gitlab instance isn’t launching properly. Have you looked at the logs from that instance? In the Synology UI, you can view them from the Docker app.

[edtriccorp]

I did look at the log. The only line item I see which may or may not be relevant is:

Saving key "/home/git/data/ssh/ssh_host_key" failed: unknown or unsupported key type

Perhaps a permissions issue with the mounted volume on the host? I manually created the following directories before running docker-compose:

/volume1/gitlab/gitlab
/volume1/gitlab/redis
/volume1/gitlab/postgresql

Would you happen to know what are the suggested permissions for the container to have the access it needs to the mounted volume?

[mikeblanton]

I'd say that's what is causing the restart. I haven't tried 10.4.2 yet, though. Perhaps try 10.4.1? That's what I'm running. I'm not sure what might be causing the host_key issue.

[edtriccorp]

@mikeblanton Interesting. I just tried 10.4.1 and I am seeing the same issue.

[mikeblanton]

See #1496. Apparently it's an issue with SSH and a lack of support of RSA. Strange, though - I upgraded from 10.0.4 to 10.4.1 the other day, and I'd expect to have run into the same problem. I've got all of my files stored in /volume1/docker/gitlab. Permissions on that dir are 755. Within the container, those files are owned by the git user/git group.

I suspect you won't be able to install 10.4.x from a fresh install until #1496 is resolved.

[edtriccorp]

Thank you @mikeblanton I did see #1496 but was curious why it worked with your DS. The upgrade path vs. fresh install is interesting. I have never ran GitLab before. I was running 10.3.6 just fine but could never get email to work with my Goddaddy host. I thought "hey. new release. why not?"... Oh well...

[mikeblanton]

Did you have 10.3.6 started and working (aside from the email)? You should be able to just use the same data mount that you had in 10.3.6 to get 10.4.1 or 10.4.2 running. That really looks like the only difference between our two setups, and it doesn't appear that clean installs of 10.4.x are working.

[CrystalMethod]

Try adding something like the following to the gitlab (+postgres/redis) service to get the console log back.

    logging:
      driver: json-file
      options:
        max-size: "10m"

Or try to "fix" it in the docker daemon config.

Output of: docker info 
...
Logging Driver: db
...

[edtriccorp]

@mikeblanton Yes 10.3.6 was started and working. Unfortunately, I decided I wanted a clean install after hours and weeks of trying to get email working. I even had HTTPS working through the synology proxy and a Letsencrypt certificate. Gitlab email worked with port 80 settings but the minute I tried to switch over to SSL/587 email would stop but everything else was as expected.

I just went back to 10.3.6. Installed and worked as before. Now if I can only figure out SMTP email with TLS.

[mikeblanton]

@edtriccorp now that you have 10.3.6 up and running, you should be able to upgrade to 10.4.2 using the same data directory. Email should work as well - I’m sending email from my install, but I’m using gmail. We can troubleshoot that under a different ticket.

[edtriccorp]

@mikeblanton Thank you sir. I can confirm that upgrading to 10.4.2 from 10.3.6 works. I have not requested help on email because I think it is a lack of understanding on my end. Things seem very confusing in the Synology world. Is opening an issue here the right thing for me to do? I thought this channel was mainly for reporting potential bugs rather than seeking help? i.e. my lack of understanding is not a bug :) I posted on the Synology forum and the GitLab forum some time ago but the questions have gone unanswered so far.