Explore >> Select a destination
|
You are here 
|
pliutau.com | ||
| | | | |
billglover.me
|
|
| | | | | Docker has had the ability to build multi-architecture images for a while. I've never had cause to use it, until now. In this post I'll walk through building a docker image that should work on your laptop and a Raspberry Pi. | |
| | | | |
infinitedigits.co
|
|
| | | | | A lightweight Dockerfile for Golang apps. | |
| | | | |
philiplaine.com
|
|
| | | | | 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
|
|
| | | 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. | ||
