/explore
|
You are here 
|
hjr265.me | ||
| | | | |
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. | |
| | | | |
paul.totterman.name
|
|
| | | | | Like many other developers, I have to work with computers with different processor architectures. For me it's amd64 (x86_64) on the laptop and arm64 (aarch64) on the server. For some it may be the other way around. Fortunately I mostly write Go, which makes cross-compilation quite easy. Docker adds some extra steps, but is very nice for deploying software. | |
| | | | |
chipx86.blog
|
|
| | | | | Here's a very quick, not exactly comprehensive tutorial on building Docker images using multiple hosts (useful for building multiple architectures). If you're an expert on docker buildx, you may know all of this already, but if you're not, hopefully you find this useful. We'll make some assumptions in this tutorial: We want to build a... | |
| | | | |
andrewlester.net
|
|
| | | Deploying a SvelteKit application to GitHub Pages. | ||
