sameersbn / sameersbn/docker-gitlab
Running docker-gitlab in Swarm
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
First of all awesomejob with the containers guys.
I'm trying to setup sameersbn/docker-gitlab in swarm mode.
I got a swarm with 3 Nodes:
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS
0bao930u0s30x5mwcysl0spta * manager1 Ready Active Leader
0e5dwbu80ql9qecz4qaqu2yd9 worker1 Ready Active
20jj008m8so8rrjyrdo0em6tn worker2 Ready Active
My docker version:
Client:
Version: 1.12.1
API version: 1.24
Go version: go1.6.3
Git commit: 23cf638
Built: Thu Aug 18 05:02:53 2016
OS/Arch: linux/amd64
Server:
Version: 1.12.1
API version: 1.24
Go version: go1.6.3
Git commit: 23cf638
Built: Thu Aug 18 05:02:53 2016
OS/Arch: linux/amd64
administrator@manager1:~/gitlab$
My volumes:
DRIVER VOLUME NAME
local c94d6d9caebba5359daf01920c217f392963b4e46e9bae246c3f30f2c932376d
vmdk gitlab_gitlab
vmdk gitlab_volume1
vmdk gitlab_volume2
vmdk volume1
vmdk volumes are global.
My networks:
NETWORK ID NAME DRIVER SCOPE
5bc78a106577 bridge bridge local
32c247f4af14 docker_gwbridge bridge local
4ufv40zbk82n gitlab overlay swarm
75773f873ee7 host host local
asghmf8eoj2j ingress overlay swarm
ae27ae789514 none null local
Now I start deploying:
sudo docker service create --name gitlab-postgresql --replicas 1 --network gitlab --env 'DB_NAME=gitlabhq_production' --env 'DB_USER=gitlab' --env 'DB_PASS=securepassword' --env 'DB_EXTENSION=pg_trgm' --mount src=volume1,dst=/var/lib/postgresql,volume-driver=vmdk sameersbn/postgresql:9.5-1
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR
bzkcvdhly2xwimy9o3m40yjxb gitlab-postgresql.1 sameersbn/postgresql:9.5-1 worker1 Running Running 2 hours ago
sudo docker service create --name gitlab-redis --network gitlab --mount src=gitlab_volume1,dst=/var/lib/redis,volume-driver=vmdk sameersbn/redis:latest
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR
ag1lfbozggzgs75ctk70onr7z gitlab-redis.1 sameersbn/redis:latest manager1 Running Running 2 hours ago
sudo docker service create --name gitlab --publish 10022:22 --publish 10080:80 --env 'GITLAB_PORT=10080' --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_SECRETS_DB_KEY_BASE=12345678901234567890asdfghjkl' --env 'GITLAB_SECRETS_SECRET_KEY_BASE=12345678901234567890asdfghjkl' --env 'GITLAB_SECRETS_OTP_KEY_BASE=12345678901234567890asdfghjkl' --network gitlab --mount src=gitlab_gitlab,dst=/home/git/data,volume-driver=vmdk sameersbn/gitlab:8.11.5
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR
1w92vcv0k2wix0fii6kxx5mvj gitlab.1 sameersbn/gitlab:8.11.5 worker2 Running Starting less than a second ago
ams74kv3ehcj6284ko2tyqw3x \_ gitlab.1 sameersbn/gitlab:8.11.5 worker2 Shutdown Failed 5 seconds ago "task: non-zero exit (1)"
c1xflvt5e5xvpxppkudjn4bgg \_ gitlab.1 sameersbn/gitlab:8.11.5 worker2 Shutdown Failed 21 seconds ago "task: non-zero exit (1)"
And this keeps going on ...
Any help would be appreciated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the three docker service create commands and the failing sameersbn/gitlab:8.11.5 task on worker2. Inspect the service task logs and compare the GitLab service with the PostgreSQL and Redis services; done means identifying the cause of the repeated non-zero exit and documenting a working Swarm deployment or confirmed image limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100