docker

9 posts

docker

Monolithic docker-compose files filtered with profiles

Those of us who use docker-compose to manage our fleets of containers generally fall into two camps. Camp A prefers one monolithic docker-compose file per host using docker-compose <command> <service> to interact with each service. Camp B split up their configuration into multiple files with some kind of logical grouping which makes sense to them. This post will provide an overview of using profiles with docker-compose to address multiple services within a monolithic file. This aims to provide

synology

Access a Synology NAS with Traefik on DSM7

With the recent update to DSM7 my Synology NAS has been transformed. It now runs a recent version of docker, I can use Ansible to manage docker-compose like I do with all my other systems and it now runs systemd! I use Traefik as my reverse proxy of choice, I understand it well and use it everywhere across about a dozen hosts - both at home and in the cloud. So it's logical to me to use Traefik to handle reverse proxying and TLS certification with the Synology box I have - the DS1621+. Pre-re

traefik

Traefik v2 and external services like Home Assistant and Blue Iris

I recently made the switch from the nginx reverse proxy life to Traefik. I've written a couple of other posts recently about the process: * Running Unifi controller behind Traefik * Running InvoiceNinja behind Traefik Today's post is going to cover the final piece of the jigsaw I needed to solve before I could dump nginx, the file provider. In otherwords - how do I use Traefik to route traffic for services that aren't containers or published via another service discovery backend? In the case