Gitlab 9.5 container registry with amazon S3

After some struggles with some missing documentation I finally did it.

Step 1

Create a bucket and an IAM-User with the recommended policy from

#Step 2
Use this conf in /etc/gitlab/gitlab.rb: (Don’t forget the region)

registry['storage'] = {
  's3' => {
    'accesskey' => 'ACCESS_KEY',
    'secretkey' => 'SECRET_ACCESS_KEY',
    'bucket' => 'S3_BUCKET_NAME',
    'region' => 'S3_REGION' # e.g. 'eu-central-1'

Step 3

(This is the step that drove me almost mad)
Create a folder named “test” in the bucket

Step 4

Start your CI and enjoy your success!

Microservice Development Environment on OSX

If you are a Mac user who likes the feeling of deleting stuff and have drunken the docker inc. kool-aid (i.e. implementing microservice architecures on top of the “docker-toolbox”) this just might mean a breath of fresh air for you as well:

  1. uninstall vagrant
  2. trash your “favourite” hypervisor (vmware, virtualbox, etc) with it
  3. learn about the existence of the lean xhyve built on top of Apple’s own hypervisor framework (only on OSX 10.10+)
  4. dlite and docker-compose your docker development containers
  5. docker-compose up  yourself towards getting some programming done again


Post by dlite creator Nathan LaFreniere – Simplifying Docker on OS X

Boot2docker and inotify

I recently ran into a problem with a compile-on-filesystem-change application on boot2docker. Due to the layered structure of boot2docker (Host->VM->docker) the mechanics required for inotify are not working.

Luckily there exists a solution:

I use docker-compose – so after installing docker-osx-dev, just run it in the folder containing the docker-compose.yml and docker-osx-dev finds the correct folders to watch.