Docker
I like to host all of my services using docker.
Installation
Installation of docker within Ubuntu Server is done so by following the instructions on the official docker documentation site
My servers are either running Ubuntu Server or Debian. Below are links to the official installation instructions for both.
Once installed, running docker --version should then return something similar to the following:
Network Configuration
Before spinning up some docker containers, I need to ensure I have setup my docker networks.
I use 4 docker networks (2 on titan, 1 on phobos & 1 on tethys)
Titan
Titan runs a Reverse Proxy in the form of Traefik. To ensure that all applications (that need to be proxied) pass through Traefik, I would need to associate them with this network.
The creation of the network is a simple command and is one that specifies a subnet.
The reason for specifying a subnet is so I can provide a static IP Address to each of my services. This also assists with connectivity between containers and keeps everything organised.
docker network create --subnet 172.19.0.0/24 proxy
docker network create --subnet 172.18.0.0/24 monitoring
This creates a /24 subnet named proxy and a /24 subnet named monitoring
Phobos
The "phobos-network" docker network has been created for all of the containers running on phobos
Just like Titan containers, they have all been provided with static IP Addresses.
As this is a totally seperate system, I'm unable to associate docker containers here with the network that traefik is running on. Therefore, any container that needs to run through traefik, a dynamic file needs to be created.
This creates a /24 subnet named phobos-network
Tethys
Similally with Phobos, I also have created a docker network for containers running on Tethys.
This creates a /24 subnet named tethys-networkDocker Commands
I deploy all of my docker containers using docker compose.
This is where I will write out everything the container needs in a YAML file.
To pull and deploy the image according to the details in the YAML, from the same directory as where the compose file resides, I would run the following command:
The -d at the end will run the container detached meaning the terminal window can be closed and the container will continue running.
Should I need to make changes to my YAML configuration (change some environment settings or change the docker image being used), I can re-deploy the container with a similar command:
This will ensure the container is re-created.
Compose Files
All of my compose files reside in the following locations
Titan
/ssd/docker-compose/
├── arrs
│ └── docker-compose.yml
├── dozzle
│ └── docker-compose.yml
├── ghost
│ └── docker-compose.yml
├── ha
│ └── docker-compose.yml
├── homepage
│ └── docker-compose.yml
├── homers
│ └── docker-compose.yml
├── it-tools
│ └── docker-compose.yml
├── navidrome
│ └── docker-compose.yml
├── overseerr
│ └── docker-compose.yml
├── phpmyadmin
│ └── docker-compose.yml
├── plex
│ └── docker-compose.yml
├── podgrab
│ └── docker-compose.yml
├── ppe
│ └── docker-compose.yml
├── sabnzbd
│ └── docker-compose.yml
└── tautulli
└── docker-compose.yml
15 directories, 15 files
Phobos
/ssd/docker/docker-compose/
├── checkmk
│ └── docker-compose.yml
├── cloudflare
│ └── docker-compose.yml
├── dockpeek
│ └── docker-compose.yml
├── dozzle-agent
│ └── docker-compose.yml
├── frigate
│ └── docker-compose.yml
├── headscale
│ └── docker-compose.yml
├── kuma
│ └── docker-compose.yml
├── mkdocs
│ └── docker-compose.yml
├── monitoring
│ └── docker-compose.yml
├── motioneye
│ └── docker-compose.yml
├── nebula-sync
│ └── docker-compose.yml
├── nginx
│ └── docker-compose.yml
├── pihole
│ └── docker-compose.yml
├── portainer
│ └── docker-compose.yml
├── ubuntu
│ └── docker-compose.yml
├── vaultwarden
│ └── docker-compose.yml
└── wazuh-agent
├── config
│ └── wazuh-agent-conf
└── docker-compose.yml
10 directories, 11 files
Tethys
/home/xander/docker/docker-compose/
├── checkmk
│ └── docker-compose.yml
├── dozzle-agent
│ └── docker-compose.yml
└── portainer
└── docker-compose.yml
3 directories, 3 files
Appdata
All of my containers have their data stored in the following locations (which are referenced in their respective compose files)
Titan
/ssd/docker/appdata/
├── dozzle
│ └── data
├── ghost
│ ├── db
│ │ ├── db-default
│ │ ├── db-lenny-sal
│ │ ├── db-stan-sal
│ │ └── db-xms
│ ├── default
│ ├── lenny-sal
│ ├── stan-sal
│ └── xms
├── ha
│ └── config
├── homepage
│ ├── app
│ ├── bookmarks.yaml
│ ├── custom.css
│ ├── custom.js
│ ├── docker.yaml
│ ├── icons
│ ├── images
│ ├── kubernetes.yaml
│ ├── logs
│ ├── proxmox.yaml
│ ├── services.yaml
│ ├── settings.yaml
│ └── widgets.yaml
├── homers
│ └── config.toml
├── Lidarr
├── monitoring
│ ├── docker-compose.yml
│ ├── grafana
│ │ └── grafana-data
│ └── prometheus
│ └── prometheus.yml
├── Navidrome
│ ├── cache
│ │ ├── backgrounds
│ │ ├── images
│ ├── navidrome.db
│ ├── navidrome.db-shm
│ ├── navidrome.db-wal
│ └── plugins
├── overseerr
│ └── config
│ ├── db
│ ├── logs
│ └── settings.json
├── phpmyadmin
│ ├── config.user.inc.php
│ └── custom
│ └── phpmyadmin
│ └── theme
├── Plex
│ └── Library
│ └── Application Support
│ └── Plex Media Server
├── podgrab
│ └── config
│ ├── backups
│ └── podgrab.db
├── portainer
│ └── data
├── Radarr
├── Readarr
├── Sonarr
├── Tautulli
├── traefik
│ ├── data
│ │ ├── acme.json
│ │ ├── traefik.yml
│ │ └── traefik.yml.bak
│ ├── docker-compose.yml
│ ├── dynamic
│ │ ├── app-blog-lenny-sal.yml
│ │ ├── app-blog-stan-sal.yml
│ │ ├── app-blog-xms.yml
│ │ ├── app-cctv.yml
│ │ ├── app-cmk.yml
│ │ ├── app-docs.yml
│ │ ├── app-dozzle.yml
│ │ ├── app-graphs.yml
│ │ ├── app-kuma.yml
│ │ ├── app-phpmyadmin.yml
│ │ ├── app-pihole1.yml
│ │ ├── app-pihole2.yml
│ │ ├── app-pihole3.yml
│ │ ├── app-portainer-phobos.yml
│ │ ├── app-portainer-tethys.yml
│ │ ├── app-prom.yml
│ │ ├── app-ubuntu.yml
│ │ ├── app-unifi.yml
│ │ ├── app-vaultwarden.yml
│ │ ├── app-wazuh.yml
│ │ ├── app-workout.yml
│ │ ├── config.yml
│ │ └── tls.yml
│ └── logs
│ ├── access.log
│ └── traefik.log
└── wazuh
└── wazuh-docker
Phobos
/ssd/docker/appdata/
├── frigate
│ └── config
├── headscale
│ ├── config
│ │ └── config.yaml
│ └── data
├── kumav2
│ ├── db-config.json
│ ├── docker-tls
│ ├── kuma.db
│ ├── kuma.db-shm
│ ├── kuma.db-wal
│ ├── screenshots
│ └── upload
│ ├── logo1.png
│ └── logo2.png
├── motioneye
│ ├── etc
│ │ ├── camera-1.conf
│ │ ├── camera-2.conf
│ │ ├── motion.conf
│ │ ├── motioneye.conf
│ │ ├── prefs.json
│ │ └── tasks.pickle
│ └── shared
│ └── recordings
├── nginx
│ ├── bicycle_crunches.gif
│ ├── crunch_kicks.gif
│ ├── done.gif
│ ├── flutter_kicks.gif
│ ├── index.html
│ ├── jumping_jacks.gif
│ ├── knee_sit_ups.gif
│ ├── plank.gif
│ └── rest.gif
├── pihole
│ ├── etc-dnsmasq.d
│ └── etc-pihole
├── portainer_data
└── vaultwarden
└── data
Tethys
~/docker/appdata/
├── checkmk
│ ├── cmkxms
│ └── plugins
│ └── mk_docker.py
├── portainer
└── portainer_data
Across all hosts, you will see here that there are numerous services listed that are not mentioned or detailed within this documentation site. These are services/applications that I am still either testing or refining.
If I plan on implmenting them long term then I will be creating pages for these.