VSHN.timer #208: Optimize your Containers

Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.

This week we’re going to talk about advanced container scenarios pushing the limits of Cloud Native technology.

1. When running Go in containers, it’s important to set CPU limits. It’s also important to ensure that the Go runtime is aware of these limits by setting a sensible GOMAXPROCS value, or to use a library like automaxprocs. River Phillips explains in detail what happens when you don’t.

https://www.riverphillips.dev/blog/go-cfs/

2. Did you know that Gitea Actions are almost fully compatible with GitHub Actions? And that Gitea also offers an integrated OCI compliant container registry? Our CTO Tobias Brunner explains how to use Gitea Actions to build and store containers.

https://tobru.ch/gitea-actions-container-builds/

3. Are you using Ruby on Rails? In that case, you might have noticed that since version 7.1 the rails new command generates a Dockerfile for your project, ready for production use. This Dockerfile is not intended for development; use Docked Rails for that!

https://www.infoworld.com/article/3706871/ruby-on-rails-extends-docker-support.html

4. K2D is a Kubernetes to Docker translator, created to solve a very specific problem: to enable the use of Kubernetes primitives on resource-constrained compute devices used in industrial IoT use cases.

https://k2d.io/

5. The VSHN.timer tool of the week is Docker-Hub-frolvlad/docker-alpine-glibc, a container image based on Alpine but with glibc built-in instead of musl. Useful if you are not interested in using debian-slim or other similar lightweight images as a base.

https://github.com/Docker-Hub-frolvlad/docker-alpine-glibc

Are you more of a musl or a glibc kind of DevOps engineer? How do you optimize your containers for your chosen programming language? Would you like to share some container tips and tricks with our readers? Get in touch with us, and see you next week for another edition of VSHN.timer.

PS: check out our previous VSHN.timer editions about containers: #12, #17, #40, #51, #54, #71, #81, #108, #124, #144, #151, #166, and #186.

PS²: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.

PS³: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.