This role allow to define unit files in yml (similar to docker compose) and generate systemd unit on remote hosts. This could be taken as a very simple and light but powerfull orchestration system.
- Docker daemon installed on host system
$ ansible-galaxy install kibatic.docker-systemd
# Default docker volumes mounted on each container
# /etc/localtime is required to share host timezone to containers
default_volumes:
- /etc/localtime:/etc/localtime:ro
# Directory where all container data will be stored: volumes, uploaded config files, ...
container_data_home: '/home/cloud/containers'
# Default options passed to docker run
default_docker_options: ''
# Default labels set on each container
default_docker_labels: []
# Default network name
default_network_name: default_network
# Units to be removed from system
removed_units: []
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
- hosts: my.awsome.host.example.com
roles: [ kibatic.docker-systemd ]
vars_files: [ vars/units/my-awsome-service/units.yml ]
tags:
- my-awsome-service
# This line ensure a removed service is not present on the system
- hosts: my.awsome.host.example.com
roles: [ kibatic.docker-systemd ]
vars:
removed_units:
- my-removed-service
systemd_units:
- name: symfony_web
image: my_awsome_symfony_image
restart_unit: true # whether to restart unit when running role or not (could be dangerous on sql clusters)
host_copy: []
environment:
SYMFONY__DATABASE__HOST: symfony_db
SYMFONY__DATABASE__USER: root
SYMFONY__DATABASE__PASSWORD: root
SYMFONY__DATABASE__NAME: demo
- name: symfony_db
image: mysql:5.5
host_copy: []
environment:
MYSQL_ROOT_PASSWORD: root
MYSQL_DATABASE: demo
MIT