\/Users<\/code> mounted automatically) – but you are unable to manage permissions from the VM. So when you install \/ run GitLab from Sameer Naik’s excellent work<\/a> you will run into the problem of PostgreSQL trying to change ownership on mounted file volumes. It simply doesn’t work under docker-machine.<\/p>\nYou can get around the problem by making the VM larger (larger disk) but then if you dump your GitLab VM you lose your Git repositories! Not a good plan.<\/p>\n
So my approach? It is to mount additional, persistent disks to the docker-machine VM and then present those disks to the relevant containers.<\/p>\n
Step 1 – Create a Persistent Disk<\/h3>\n
My “persistent disk” is simply a VDI created through VirtualBox in a known folder. Here’s the code:<\/p>\n
\r\n# create local folder on host which can be shared with docker.\r\n# see https:\/\/github.com\/docker\/machine\/issues\/1826 for mac osx description\r\nif [ ! -s \/srv\/docker\/sab-data-01.vdi ]; then\r\n echo 'Create VDI...'\r\n sudo mkdir -p \/srv\/docker\r\n sudo VBoxManage createhd --filename \/srv\/docker\/sab-data-01.vdi --size 65536 --format vdi --variant Standard\r\n sudo chmod 777 \/srv\/docker\/sab-data-01.vdi\r\nfi\r\n<\/code><\/pre>\nI create the VDI to be a max of 64GB – but it’s a dynamic disk so won’t be any bigger than is necessary.<\/p>\n
Step 2 – Start \/ Attach docker-machine<\/code><\/h3>\nWhen you run docker-machine, you very well can get a brand-new proxy VM created for you. So my next task is to make sure that docker-machine is running and then attach my VDI to it. Here’s some code:<\/p>\n
\r\n# are we started?\r\nl_docker_machine=$(docker-machine ls --quiet)\r\nif docker-machine status $l_docker_machine 2>\/dev\/null | grep --quiet -e 'Stopped'; then\r\n echo 'Start Docker machine...'\r\n docker-machine start\r\n l_docker_machine=$(docker-machine ls --quiet)\r\nfi\r\n\r\n# are we attached?\r\nl_needs_restart=0\r\nif ! VBoxManage showvminfo $l_docker_machine 2>\/dev\/null | grep --quiet -e '\/srv\/docker\/sab-data-01.vdi'; then\r\n echo 'Attach to Docker...'\r\n VBoxManage storageattach $l_docker_machine --storagectl \"SATA\" --device 0 --port 2 --type hdd --medium \/srv\/docker\/sab-data-01.vdi\r\n l_needs_restart=1\r\nfi\r\n<\/code><\/pre>\nStep 3: Initialize the Disk<\/h3>\n
On first-run, we have an uninitialized disk attached to the docker-machine VM. Let’s initialize it using good old ext4 (use anything you like; xfs, btrfs). <\/p>\n
\r\n# do we need to init the disk?\r\nl_sdb1_init=$(docker-machine ssh $l_docker_machine '! blkid \/dev\/sdb1 && echo 1' 2>\/dev\/null | grep UUID)\r\nif [ x\"$l_sdb1_init\" = x ]; then\r\n echo 'Initialize sdb1 on Docker...'\r\n docker-machine ssh $l_docker_machine '(echo n;echo p;echo 1;echo;echo;echo w; echo q) | sudo fdisk \/dev\/sdb' 2>\/dev\/null\r\n docker-machine restart $l_docker_machine \r\n docker-machine ssh $l_docker_machine 'sudo mkfs.ext4 \/dev\/sdb1' 2>\/dev\/null\r\n l_needs_restart=1\r\nfi\r\nl_sdb1_UUID=$(docker-machine ssh $l_docker_machine 'sudo blkid \/dev\/sdb1' 2>\/dev\/null | awk '{print $2}' | sed -e 's#^UUID=\"\\([^\"]\\+\\).*#\\1#')\r\n<\/code><\/pre>\nOnce the disk is initialized, I have found I must restart the docker-machine VM:<\/p>\n
\r\nif [ $l_needs_restart -eq 1 ]; then\r\n echo 'Restart Docker machine...'\r\n docker-machine restart $l_docker_machine \r\n l_needs_restart=0\r\nfi\r\n<\/code><\/pre>\nNext – I must ensure that the disk is mounted. This *appears* to be persistent (remounted) across docker-machine VM restarts, but (of course) must be performed both on first-run as well as any time that the actual underlying docker-machine VM is recreated (which can happen regularly).<\/p>\n
\r\n# we do need to mount the disk...check\r\nif ! docker-machine ssh $l_docker_machine 'sudo mount' 2>\/dev\/null | grep --quiet -e '\/dev\/sdb1'; then\r\n echo 'Mount \/dev\/sdb1...'\r\n docker-machine ssh $l_docker_machine 'sudo mount \/dev\/sdb1 \/mnt\/sdb1'\r\nfi\r\n<\/code><\/pre>\nFinally – let’s initialize the folder structure on the disks. We want space for all the GitLab components: PostgreSQL, Redis, and GitLab itself:<\/p>\n
\r\n# create our folders - logic is in there to clean out existing folders (you'd need a backup!)\r\nl_needs_sab_gitlab_folders=$(docker-machine ssh $l_docker_machine '[ ! -d \/mnt\/sdb1\/sab-gitlab ] && echo 1' 2>\/dev\/null)\r\nif [ x\"$l_needs_sab_gitlab_folders\" = x1 ]; then\r\n echo 'Create sab-gitlab folders....'\r\n docker-machine ssh $l_docker_machine 'sudo mkdir -p \/mnt\/sdb1\/sab-gitlab' 2>\/dev\/null\r\n docker-machine ssh $l_docker_machine 'sudo mkdir -p \/mnt\/sdb1\/sab-gitlab\/postgresql \/mnt\/sdb1\/sab-gitlab\/redis \/mnt\/sdb1\/sab-gitlab\/data' 2>\/dev\/null\r\n docker-machine ssh $l_docker_machine 'sudo mkdir -p \/mnt\/sdb1\/sab-gitlab\/postgresql \/mnt\/sdb1\/sab-gitlab\/redis \/mnt\/sdb1\/sab-gitlab\/data; sudo chmod -R 777 \/mnt\/sdb1\/sab-gitlab' 2>\/dev\/null\r\nfi\r\n<\/code><\/pre>\nCreate GitLab Containers<\/h3>\n
The next step is to create \/ restart our GitLab containers. I use three of them as mentioned above.<\/p>\n
First – let’s make sure we can use the docker<\/code> command (by evaluating the docker-machine environment):<\/p>\n\r\n# load docker command\r\neval $(docker-machine env)\r\n<\/code><\/pre>\nIn the following examples, I specify “volumes” (automatically-mounted host directories) from the VDI I configured on the docker-machine VM.<\/p>\n
First – let’s start the PostgreSQL container. Our logic checks to see if we already have the container and – if so – we restart it:<\/p>\n
\r\n# launch postgresql or restart - important to provide pg_trgm extension\r\nif docker ps -a -f 'name=sab-gitlab-postgresql' 2>\/dev\/null | grep --quiet -e 'sab-gitlab-postgresql$'; then\r\n echo 'Start postgresql...'\r\n docker start 'sab-gitlab-postgresql'\r\nelse\r\n echo 'Run postgresql...'\r\n docker run --name sab-gitlab-postgresql -d \\\r\n --env 'DB_NAME=gitlabdb' \\\r\n --env 'DB_EXTENSION=unaccent,pg_trgm' \\\r\n --env 'DB_USER=gitlab' --env 'DB_PASS=password' \\\r\n --volume \/mnt\/sdb1\/sab-gitlab\/postgresql:\/var\/lib\/postgresql \\\r\n sameersbn\/postgresql:latest\r\nfi\r\n<\/code><\/pre>\nNext – let’s do the same thing for Redis:<\/p>\n
\r\n# Launch a redis container\r\nif docker ps -a -f 'name=sab-gitlab-redis' 2>\/dev\/null | grep --quiet -e 'sab-gitlab-redis$'; then\r\n echo 'Start redis...'\r\n docker start 'sab-gitlab-redis'\r\nelse\r\n echo 'Run redis...'\r\n docker run --name sab-gitlab-redis -d \\\r\n --volume \/mnt\/sdb1\/sab-gitlab\/redis:\/var\/lib\/redis \\\r\n sameersbn\/redis:latest\r\nfi\r\n<\/code><\/pre>\nAnd, of course, we want to run GitLab. Note that I’m publishing ports 10080 (Web) and 10022 (for SSH access). Also, note that I use the --link<\/code> option to connect the GitLab container to the Redis and PostgreSQL containers:<\/p>\n\r\n# launch gitlab\r\nif docker ps -a -f 'name=sab-gitlab' 2>\/dev\/null | grep --quiet -e 'sab-gitlab$'; then\r\n echo 'Start gitlab...'\r\n docker start 'sab-gitlab'\r\nelse\r\n echo 'Run gitlab...'\r\n docker run --name sab-gitlab -d \\\r\n --link sab-gitlab-postgresql:postgresql --link sab-gitlab-redis:redisio \\\r\n --publish 10022:22 --publish 10080:80 \\\r\n --env 'GITLAB_PORT=10080' --env 'GITLAB_SSH_PORT=10022' \\\r\n --env 'GITLAB_SECRETS_DB_KEY_BASE=long-and-random-alpha-numeric-string' \\\r\n --volume \/mnt\/sdb1\/sab-gitlab\/data:\/home\/git\/data \\\r\n sameersbn\/gitlab:latest\r\nfi\r\n<\/code><\/pre>\nAnd it all works. I’ve taken the liberty of adding a new \/etc\/hosts<\/code> entry that points to sad-gitlab.softwareab.local<\/code>.<\/p>\nHere’s the login page:
\n![\"sab-gitlab-010\"](\"\/wordpress\/wp-content\/uploads\/2016\/05\/sab-gitlab-010-300x290.png\")
<\/a><\/p>\n
![\"sab-gitlab-020\"](\"\/wordpress\/wp-content\/uploads\/2016\/05\/sab-gitlab-020-300x272.png\")
<\/a><\/p>\n