Docker

Installation

If you haven't installed Docker yet, see Docker's Getting Started page on how to install it.

Quirks

Systemd services not running after initial provisioning

Due to the way systemctl3.py monitors services, it is not able to properly monitor and restart services that (expectedly) terminate during initial provisioning.

To get services working, restart the container by running (on the host):

vagrant halt && vagrant up --provider=docker

The above should only be needed the first time provisioning a new container.

Systemd service status appears inactive

There is a known bug with systemctl3.py that causes services to incorrectly appear as "inactive (dead)" when checking their status using systemctl.

The workaround is to always use sudo when checking the status:

sudo systemctl status example.service

See also issue #13 for more discussion around some of these quirks.

File permissions errors if Git repo checked out as root on host

Don't checkout the code as root, on the host machine. It will cause file permissions errors in Docker.