Containers

Wading through the world of containers is a journey in itself...

I'm in my early stages in learning about containers and learn new things constantly, i have managed to build and maintain some container images that i do use myself.

The containers should work on any container system, they are built and run with podman in rootless mode in my environment to make sure they do not require any high privilege system settings on the host side to work.

Below is a short description about them and a link to where they reside on Docker Hub.

Bind-DNS

A Bind DNS container built with the purpose to enable custom DNS usage primarily for containers, can also be used as internal DNS server, only downside is that Windows clients have issue with lookups on other ports than 53 and best is to route port 53 to the container in question, this will limit it to just 1 DNS server per container host, more info at the Docker Hub page.

Link: DockerHub

MkDocs-Materials

A Development container for Markdown documents, uses MkDocs and the Materials plugin as the primary tools used. Has the ability to build a site in html for publishing on an external facing site, like this one.

Has SSH access for easy site development using any tool that supports SSH connection directly to the container, like Visual Studio Code.

Link: DockerHub

Folding@Home

Container with the Folding@home client ready to fold. uses the 7.x version of the client for now, the new 8.x has some issues in the way they are forcing you to use cloud GUI to see status of your folding server and it only works with a single local folding instance that runs on the same machine where you use the web GUI.

The 7.x do not suffer from that issue and has separate GUI access for each container.

Link: DockerHub