Docker
I like to host all of my services using docker.
Installation
Installation of docker is done so by following the instructions on the official docker documentation site
My servers are running Debian. Below are links to the official installation instructions.
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.
Below are example of some of the docker networks I have created and the commands used.
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.
```sh
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
The "phobos-network" docker network has been created for all of the containers running on phobos
As this is a totally seperate host, 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.
```sh
docker network create --subnet 172.20.0.0/24 phobos-network
docker network create --subnet 172.18.0.0/24 monitoring
```
This creates a /24 subnet named phobos-network and a /24 subnet named monitoring
The "tethys-network" docker network has been created for all of the containers running on tethys
As this is a totally seperate host, 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.
```sh
docker network create --subnet 172.20.0.0/24 tethys-network
docker network create --subnet 172.18.0.0/24 monitoring
```
This creates a /24 subnet named tethys-network and a /24 subnet named monitoring
My primary Pi-Hole also runs docker and in keeping with the other servers, this also has a docker networks and subnets specified.
```sh
docker network create --subnet 172.21.0.0/24 pihole1-network
docker network create --subnet 172.18.0.0/24 monitoring
```
This creates a /24 network named pihole1-network & and a /24 subnet named monitoring
The reason for specifying subnets 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 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:
```sh
docker compose pull; docker compose up -d
```
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:
```sh
docker compose pull; docker compose up -d --force-recreate
```
This will ensure the container is re-created.
Compose Files
All of my compose files and the containers appdata reside in the following locations
```sh
/ssd/docker/docker-compose/
.
├── arrs
│ └── docker-compose.yml
├── fail2ban
│ └── docker-compose.yml
├── ghost
│ └── docker-compose.yml
├── guacamole
│ └── docker-compose.yml
├── home-assistant
│ └── docker-compose.yml
├── it-tools
│ └── docker-compose.yml
├── minecraft
│ └── docker-compose.yml
├── monitoring
│ └── docker-compose.yml
├── navidrome
│ └── docker-compose.yml
├── phpmyadmin
│ └── docker-compose.yml
├── plex
│ └── docker-compose.yml
├── podgrab
│ └── docker-compose.yml
├── README.md
├── sabnzbd
│ └── docker-compose.yml
├── seerr
│ └── docker-compose.yml
├── tautulli
│ └── docker-compose.yml
├── titan-mysql-db
│ └── docker-compose.yml
├── tracearr
│ └── docker-compose.yml
├── traefik
│ └── docker-compose.yml
└── traefik-manager
└── docker-compose.yml
20 directories, 21 files
```
```sh
/ssd/docker/docker-compose/
.
├── homepage
│ └── docker-compose.yml
├── ipam-backend
│ ├── docker-compose.yml
│ ├── Dockerfile
│ ├── package.json
│ └── server.js
├── 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
├── ollama
│ └── docker-compose.yml
├── ph-intercept
│ └── docker-compose.yml
├── phobos-mysql-db
│ └── docker-compose.yml
├── phpmyadmin
│ └── docker-compose.yml
├── pihole
│ └── docker-compose.yml
└── portainer
└── docker-compose.yml
14 directories, 17 files
```
```sh
/ssd/docker/docker-compose/
.
├── checkmk
│ └── docker-compose.yml
├── monitoring
│ └── docker-compose.yml
└── portainer
└── docker-compose.yml
3 directories, 3 files
```
```sh
/home/xander/docker/docker-compose
.
├── portainer
│ └── docker-compose.yml
└── wireguard-exporter
└── docker-compose.yml
3 directories, 2 files
```
Appdata
```sh
/ssd/docker/appdata/
.
├── dozzle
├── fail2ban
├── ghost
├── ha
├── homepage
├── homers
├── Lidarr
├── minecraft
├── Navidrome
├── overseerr
├── phpmyadmin
├── Plex
├── podgrab
├── portainer
├── Radarr
├── Readarr
├── SABnzbd
├── seerr
├── Sonarr
├── Tautulli
├── titan-mysql-db
├── tracearr
│ ├── backups
│ ├── db
│ └── redis
├── traefik
└── traefik-manager
29 directories
```
```sh
/ssd/docker/appdata/
.
├── homepage
├── ipam
├── kumav2
├── motioneye
├── nginx
├── ollama
├── open-webui
├── ph-intercept
├── phobos-mysql-db
├── phpmyadmin
├── pihole
├── poker
└── portainer_data
13 directories
```
```sh
/ssd/docker/appdata/
.
├── checkmk
│ ├── cmkxms
│ ├── notifications
│ └── plugins
├── monitoring
│ ├── grafana
│ ├── pihole-exporter
│ ├── prometheus
│ └── unpoller
└── portainer
└── portainer_data
11 directories
```
`no appdata directory required`
Info
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 implementing them long term then I will be creating pages for these.