Off topic, again

lilo-coffee-roasters
Lilo Coffee Roasters is good, but not as shockingly great as Glitch.
The beans were OK for me, just a bit too lightly roasted.
Maybe I’ll just buy the beans next time.

Back to the post

Recently I built a small project and wanted to run it inside a Docker container.

I was going to host this Docker container inside my homelab, but I’m too lazy to run docker build and docker run manually every time I change something.

So again, Komodo comes to the rescue

It takes your code and Dockerfile, and builds the Docker image for you.
Then it deploys it for you, all in one git push, no additional GitHub Action.

Add a builder in Komodo to build the image

  1. Go to Resources > Builders
  2. Click New Builder, set the name of your builder, and set Builder Type = Server komodo-add-builder
  3. Pick the server you want to build your Docker image at
    komodo-builder-server

Add a build profile in Komodo, which automates the build

  1. Go to Resources > Builds
  2. Fill in the necessary information
    • Builder
    • Version (You can set initial version and auto-increment the version per git push)
    • Source, account and repo
    • Image Registry (you can push to a custom image registry like Docker Hub, Nexus…)
  3. The build will look for the Dockerfile in the root of the git repo
    • If you want to change that, change the Dockerfile path
  • komodo-build-version

Yes, your instincts are right. The automation is done by webhook. Again.

  1. Just like the automatic stack deployment , enable the webhook function
  2. Set the secret, then copy the URL and secret to the Gitea project
  • komodo-build-webhook

Then you have automatic Docker image builds when you push your changes to the git repo.

Final touch: auto-deployment after build

  1. Go to Resources > Deployments
  2. Fill in the necessary information
    • Server (that hosts the Docker container; if your build destination is local, please make sure you run it on the same machine)
    • Build (Select Build in the first dropdown, then choose the build you created in the previous step)
    • Turn on “Redeploy on build” to automatically deploy after the build is complete
    • Network Mode
  • komodo-add-deployment

After filling those in, you can test it by pushing changes to the git repo
and watching the container get redeployed automatically.
komodo-auto-deployment

Maybe I want a centralized private Docker registry one day, just because it would be more convenient for building and deploying across different machines.