Explore >> Select a destination
|
You are here 
|
markentier.tech | ||
| | | | |
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. | |
| | | | |
blog.oddbit.com
|
|
| | | | | At work we have a cluster of IBM Power 9 systems running OpenShift. The problem with this environment is that nobody runs Power 9 on their desktop, and Docker Hub only offers automatic build support for the x86 architecture. This means there's no convenient options for building Power 9 Docker images...or so I thought. It turns out that Docker provides GitHub actions that make the process of producing multi-architecture images quite simple. | |
| | | | |
www.augmentedmind.de
|
|
| | | | | Improve the build speed of Docker images in CI pipelines, using BuildKit caching tricks, the .dockerignore file and package managers tweaks. | |
| | | | |
arveknudsen.com
|
|
| | | In my previous blog post I showed how to use the Kops tool to create a production ready Kubernetes cluster on Amazon Web Services (AWS). In this follow-up post I will show how to install Elasticsearch and its graphical counterpart Kibana in the cluster, in order to be able to collect and store logs from your cluster and search/read them. We will also install Fluentd as this component is responsible for transmitting the standard Kubernetes logs to Elasticsearch. This is generally known as the ELK stack, which stands for Elasticsearch, Logstash (precursor to Fluentd) and Kibana. | ||
