/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 www.perrotta.dev
Docker build: ignore cache | not just serendipity
| | actuated.dev
The efficient way to publish multi-arch containers from GitHub Actions
2.3 parsecs away

Travel
| | Learn how to publish container images for both Arm and Intel machines from GitHub Actions.
| | bioconductor.github.io
Emulated build and test of Bioconductor packages for Linux ARM64 - Bioconductor community blog
1.6 parsecs away

Travel
| | Build and test for Linux ARM64 with Docker on x86_64 host
| | philiplaine.com
Cross Compiling Docker Images Philip Laine
1.1 parsecs away

Travel
| | It has been an issue for a long time to run Docker images on multiple architectures. I remember the first time I got the idea to install Docker on my Raspberry Pi and I realized quickly that what I was trying to do would not work. The issue of course was that I was trying to use an AMD64 compiled Docker image on a ARM 32 bit CPU. Anyone who works with any lower level languages would call me an idiot for realizing this sooner than later. I would agree with them. Docker just seems to work like magic, running on most machines without any issue, like running Linux containers on Windows. One thing that has not been easy though is building Docker images on one type of CPU and running them on another.
| | hjr265.me
Configuring Docker Health Check for Go Web Applications ยท hjr265.me
12.0 parsecs away

Travel
| Docker has been providing a health check mechanism for quite some time. It is useful in identifying issues with programs that can fail in ways other than just outright crashing. And it is easy to set up. Docker health checks work periodically running a program within the container and observing its exit status. If it exits with a 0, the container is considered healthy. If it exits with a 1, the container is considered to be unhealthy.