Build a CI workflow in GitHub Actions with Buildah and Podman | Part 4 - How to live without Docker for developers

As you might already know, Kubernetes is going to drop support for Docker. Starting from version 1.20 that was recently released in December 2020 you will see a deprecation warning for Docker. Docker runtime support will be completely removed from Kubernetes in version 1.22 that will be release in late 2021. After that you will need to switch to one of the other compliant container runtimes, like containerd or CRI-O inside your clusters. Despite both containerd and CRI-O know how to pull docker images and run them and Docker Images Manifest V2 and OCI image specification are almost the same, nobody knows how long Docker images will be supported.

As developers, we need to be prepared to build either docker or OCI images in just a one click and get used to living without Docker.

Therefore I decided to create a series of videos with the common title - How to live without Docker for developers.

In the previous episodes I showed you how you can build an image from scratch using the native Buildah commands and how you can push an image manually to Docker Hub and GitHub packages using Buildah.

In this episode

In this episode I will show you how you can automate the process to push an image to a container registry and create a Continuous Integration workflow using Buildah and GitHub Actions. At first, I will push my code to Git repository on GitHub. And then I will create a workflow in GitHub Actions to build my image and push it to GitHub Packages, also known as GitHub Container Registry.

Please check it out and subscribe to my channel to be notified when my new videos will be published.

Link to the video:

Code is already published on my GitHub:

Thank you in advance.