containers

Watchtower keeps an eye on your running containers and updates them when new containers appear upstream. 📦

Although my first attempt at self-hosting Mastodon was a failure, I went back for a second attempt with docker-compose. 🧗‍♂️

My go-to method for managing containers easily is still docker-compose. It works really well on Fedora CoreOS. 📦

Ongoing changes at Twitter led me to take a second look at mastodon, including running my own mastodon instance. 🐘

Access files over NFS within kubernetes pods with a quick volume mount. 🗄

Package up graphical applications in containers and run them with podman. 🚢

Re-use the same wildcard TLS certificate for multiple containers running behind traefik. 🚦

Run rootless Linux containers without any daemons using docker-compose and podman on Fedora! 📦

Many cloud providers give you lots of memory with each instance and you can speed up tests and builds by using a ramdisk.

Buildah and podman work well with the vfs storage driver, but the default mount options can cause problems.

My team at Red Hat depends heavily on GitLab CI and we build containers often to run all kinds of tests.

Environment variables are easy to add to OpenShift deployments, but a more secure way to add these variables is by referencing a secret.

This post is the second installment in the series of What’s Happening in OpenStack-Ansible (WHOA) posts that I’m assembling each month.

The world of OpenStack moves quickly.

It seems like there’s a new way to run containers every week.

I’ve been getting involved with the Fedora Security Team lately and we’re working as a group to crush security bugs that affect Fedora, CentOS (via EPEL) and Red Hat Enterprise Linux (via EPEL).

The world of containers is constantly evolving lately.

Getting started with LXC is a bit awkward and I’ve assembled this guide for anyone who wants to begin experimenting with LXC containers in Fedora 20.