
We have found a useful Docker application for Homelab folks. It’s called IT Tools. It can be run as a Docker container. Our installation uses our Traefik reverse proxy.
The video above covers the installation via Docker Compose.
We have found a useful Docker application for Homelab folks. It’s called IT Tools. It can be run as a Docker container. Our installation uses our Traefik reverse proxy.
The video above covers the installation via Docker Compose.
We’re running a Docker container called Wallabag, which can be used to save cleanly formatted copies of web pages and articles. Smartphone (iPhone and Android) apps are available for Wallabag, making viewing the saved content easy on the go.
The following video explains what Wallbag does.
This video covers the installation of Wallabag using Docker Compose. It can run on any docker host.
This video also contains some good information on sources for other self-hosted apps.
We’re running a Docker container called RSSHub, which detects RSS feeds available on websites that we browse. You can learn more about RSS Hub here.
This page covers the installation and use of the RSSHub container and the associated RSSHub Radar Chrome browser extension.
We use the BazQux RSS Reader with our installation. The following shows our configuration for the RSS Hub Radar Chrome Extension, which is used with RSSHub –
Many of our applications and services run as Docker containers. Our monitoring dashboard solution covers two aspects of Docker container performance:
These data collectors enable several Grafana dashboards that help us manage our Docker cluster.
We run a combination of Node Exporter and cAdvisor on each Docker host VMs. These containers scrape data for our Docker hosts and feed it to the Prometheus instance in our Docker stack.
The following video explains how all of this is set up –
We are using several dashboards to implement our Docker monitoring solution.
We are using a modified version of the Grafana Dashboard above to monitor the overall performance of our Docker nodes.
We are using a modified version of the Grafana Dashboard above to monitor and enable drilling into detailed performance metrics for our Docker nodes.
We are using a modified version of the Grafana Dashboard above to monitor and enable a summary view of the containers in our Docker cluster.
We are using a modified version of the Grafana Dashboard above to monitor and enable drilling into the detailed performance of containers in our Docker cluster.
We are using a modified version of the Grafana Dashboard above to monitor and enable drilling into the performance of Windows VMs in our Docker cluster.
We set up a Grafana Dashboard to implement Proxmox Monitoring. The main components in our monitoring stack include:
The following sections cover the setup and configuration of our monitoring stack.
The following video explains how to set up a Grafana dashboard for Proxmox. This installation uses the monitoring function built into Proxmox to feed data to Influx DB.
And here is a video that explains setting up self-signed certificates –
Configuring Self-Signed Certificates
We are using the Proxmox [Flux] dashboard with our setup.
It is helpful to have access to files and directories associated with our Docker persistent volume stores. File Browser is a simple Docker container that provides a file manager.
The following video covers the installation and use of the File Browser container.
We’ve added a Grafana Monitoring and Logging system to our Home Lab. The system is based on Grafana, Prometheus, Grafana Loki, Promtail, Telegraf, and InFlux DB.
The following video covers the installation of our Grafana Monitoring and Logging monitoring stack.
Setup Logging and Monitoring in Docker
Grafana Lofi and Promtail work together to scape and store log data. These tools can scrape docker data and accept syslog data as well. The following video explains how to configure Loki and Promtail.
Configure Grafana Loki and Promtail for logs
There are a few details that we needed to do differently than the video:
The contents of /etc/docker/daemon.json are as follows:
{ "log-driver": "loki", "log-opts": { "loki-url": "http://localhost:3100/loki/api/v1/push", "loki-batch-size": "400", "loki-retries": "2", "loki-max-backoff": "800ms", "loki-timeout": "1s", "keep-file": "true", "mode": "non-blocking" } }
We have configured a combination of Loki and Promtail to accept Syslog events. Promtail does not support Syslog events using the UDP protocol. To solve this problem, we set up rsyslog running under the Ubuntu system, which hosts the Promtail Docker container, to consolidate and forward all Syslog events as a front end to Promtail. Information on configuring rsyslog as a front end to Promtail can be found here.
The following video provides some information on configuring dashboards and other monitoring capabilities.
We do a variety of software development and Java coding tasks. To make this easier and more accessible from all our computers, we will try VS Code and VS Code Server.
This tool allows editing using a web browser on any computer. The VS Code web interface is hosted from a server running in a Docker container.
The following video explains how to set up the tool and connect it to a GitHub repository.
VS Code Server Installation and Set Up
The following video suggests several useful VS Code plugin extensions.
We have created many websites and services for our Home Lab. It’s nice to have an organized dashboard to access these tools.
We use a dashboard tool called Dashy for this purpose. Dashy runs in a Docker container and is easy to configure. The following video explains how to set up and configure Dashy.