Some of the docker images I use

My own Docker images

I maintain a couple of docker images for myself on Dockerhub(about 9 active) at the following link, under user qwe1:

https://hub.docker.com/u/qwe1

Other images used

I use many images from linuxserver.io, such as sonarr, radarr, jackett and jellyfin.

Bazarr is also great to get subtitles and to be honest, it works OK most of the time.

I also like to use mariadb:10.4 and traefik:2.2.

It took me some time to get a working config for the new traefik 2.x docker image.

I had to ditch my previous method of using a toml file and some ansible hackery.

Nowadays, I just run traefik with a long command line from a docker compose file.

A traefik example from an ansible docker-compose file:

        traefik:
         image: traefik:2.2
         restart: unless-stopped
         container_name: traefik
         command:
           - "--providers.docker=true"
           - "--providers.docker.exposedbydefault=false"
           - "--entrypoints.web.address=:80"
           - "--entrypoints.websecure.address=:443"
           - "--entrypoints.web.http.redirections.entrypoint.to=websecure"
           - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
           - "--certificatesresolvers.myresolver.acme.dnschallenge=true"
           - "--certificatesresolvers.myresolver.acme.dnschallenge.provider=cloudflare"
           - "--certificatesresolvers.myresolver.acme.email={{ var1 }}"
           - "--certificatesresolvers.myresolver.acme.storage=/acme.json"
           - "--global.sendAnonymousUsage=false"
         environment:
           - CF_API_EMAIL={{ var1 }}
           - CF_API_KEY={{ var2 }}
         ports:
           - 80:80
           - 443:443
         networks:
           - desktop_network
         volumes:
           - /var/run/docker.sock:/var/run/docker.sock
           - /var/docker/traefik/acme.json:/acme.json

Some other images I use are php:7.3-apache-buster for 2 dokuwiki instances.

I also have a gitea instance running with mariadb database.

I like to wait a bit before upgrading my gitea instance to see if there are issues with a release.

I also run a pihole instance with host networking on a laptop, and it functions OK as a dns and dhcp server.

I made a mistake by leaving my pihole tag at latest, so when the latest release came out(v5.0), I accidently got upgraded to 5.0.

I haven't issues with the new version, it's just I wanted to wait a few weeks for issues to be ironed out.

I also have a draw.io image running, image:

fjudith/draw.io:alpine

I run a local version of js dencoder, which is useful for decoding some garbage URLs found on the web with httpd:alpine image.

What's special about the httpd:alpine image is that the default web root is /usr/local/apache2/htdocs, instead of /var/www/html as found in the debian based httpd images.

This caught me as a surprise when I tried running the alpine image the first time.

How I try to track docker images tags and releases

I am subscribed to a bunch of Github RSS feeds and frequently review new releases for any issues before doing any major upgrades.

Fortunately, linuxserver.io has Github repos for docker images and their git tags match their docker tags.

This is all manual and can be tedious, but I try to to avoid using latest tags where possible.

links

social