Thumbnail image

Using Github Actions to Build Containers (and host them)

Some time ago, I wrote a blog, around how to easily build and host, Docker containers using Dockers autobuild tools.

After the blog post Docker both changed to using rate limits, for API calls, but also removed the Autobuild feature.

I understand fully, that Docker is trying to find out, how to make money, but I am not a fan of the Rate limit. Imho it should be based on pulls, and not the amount of API call’s.

So I updated the blog, to show how to do this, using Gitlab runners, with a local hosted Harbor instance.

Some time ago Github announces, that you could also host Docker images, as part of their Packages offering.

I have long been wanting to look more into github Actions, but have struggled to find a usecase. But here was one, that sounded like it could be usefull.

This is a post, on how I changed to using Github Actions to build and host my Docker containers.

First off. I did not change anything in my repo, from my last blog. But if you are starting from scratch, then create a Dockerfile in your Github repo, and make sure it works. Then you are good to follow the rest of my guide.

First I disconnected the Gitlab sync, that I had been running, to have a synced repo, on both Github and Gitlab.

Then I opened the repo on github, and chosed Actions on the top. Actions menu

From here I selected “New Workflow” and then I selected the “Publish Docker Container” from the top right. Publish Docker Container

The cool thing, is that all I had to do now, was to give the file a Name, and then press “Start Commit” in the top right corner, for it to work. Action Code

The action, automaticly found my Dockerfile in the root of my Repo, build it using the repo name and branch, and pushed it to my Github Repo.

How cool is that :-)

In my case, the full url to use, when pulling it, is :

If that name does not fit you, then it’s easy to change the action, to someting that fit’s you better.

The continer is now also being build every night, and pushed to Github’s repo, so it’s aways up to date.

Since this is a public repo, there is no charge, but let’s see if that changes in the future. For now, i’m happy with my new hosted repo, can I can use without thinking about API limits, in my CI/CD pipelines.

I will still save my private images in my private Harbor registry, since it gives me some added services, with security scanning etc. But most of my images are ok in being public, and there I can see myself using this a lot more in the future. Maybe even creating small repo’s for single containers, to have an easy way of building, updating, and hosting them.

If you want to try yourself, then feel free to use my container image, or to fork the Repo to create your own version :

Hope you found this usefull.

Photo by Ian Taylor on Unsplash