Explore >> Select a destination
|
You are here 
|
pliutau.com | ||
| | | | |
www.screamingatmyscreen.com
|
|
| | | | | Timo Zimmermann talking about software engineering, leading teams, consulting and start ups. | |
| | | | |
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. | |
| | | | |
memo.mx
|
|
| | | | | Docker multi-stage build is a great way to build a container images with a minimal footprint. Compiled languages like Go or Rust can take advantage of this by just shipping a binary to a container This is an example from the official docs: FROM golang:1.16 WORKDIR /go/src/github.com/alexellis/href-counter/ RUN go get -d -v golang.org/x/net/html COPY app.go ./ RUN CGO_ENABLED=0 go build -a -installsuffix cgo -o app . FROM alpine:latest RUN apk --no-cache add ca-certificates WORKDIR /root/ COPY --from=0 /g... | |
| | | | |
pythonspeed.com
|
|
| | | When you're building Docker images you often need some secrets: a password, an SS Hkey. The secure mechanism is BuildKit; others might leak them. | ||
