Sebastiaan van Stijn Profile picture
May 2, 2019 3 tweets 2 min read Read on X
Multiple approaches for multi-platform support with buildx and buildkit #DockerCon ImageImage
cross compilation support #DockerCon Image
Build Windows, or even webassembly #DockerCon Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Sebastiaan van Stijn

Sebastiaan van Stijn Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @thaJeztah

Sep 3, 2022
@iximiuz @rumpl @Docker @solomonstre @crosbymichael The actual switch from python to Go happened before I joined the project, and I'm not sure if much of that has been documented (publicly).

I did write down some things a while back, describing why Go was a good fit for the project;
@iximiuz @rumpl @Docker @solomonstre @crosbymichael As to the move from "single binary" to splitting into multiple projects (runc, containerd), there were various reasons (some of those may have been captured in the blogposts linked elsewhere in this thread);
@iximiuz @rumpl @Docker @solomonstre @crosbymichael Originally, Docker used LXC as part of the runtime; while that got us there, there were times where it wasn't always a close fit, and at times there were portability/compatibility issues (taking into account different distros).
Read 15 tweets
Dec 3, 2020
The deprecation of docker-shim (and Docker Engine as runtime) marks the completion of a long-term commitment to provide a modern runtime for Kubernetes 1/15
When the kubernetes project was started, it chose the Docker Engine as runtime (a logical choice, as at the time, the Docker Engine was about the "only" runtime) 2/15
However, the Docker Engine was not designed with orchestration in mind, and not designed to be used as runtime for Kubernetes; the Docker Engine has many features that make sense for local development (build, run) and running non-orchestrated containers, 3/15
Read 15 tweets
Nov 25, 2020
I noticed this some time ago; happy to see this little gem being added to the @github UI

A thread on what it is, and why it's really, really useful 1/15 Image
Perhaps you have never ran into this yourself, but if you're maintaining an (open source) project on GitHub that has forks, chances are you have been "confused", or had the scare of your life because of this 2/15
I don't have full insight into how _exactly_ it's setup behind the scenes (@calavera explained it to me once, but I forgot the details); GitHub keeps references to all forks of a repository, effectively making all forks of a codebase form a single, giant git repo 3/15
Read 15 tweets
Sep 27, 2020
I saw I was mentioned, and yes, I have many thoughts about go modules. As @tiborvass mentioned; they're great... in an ideal world.

Let me write up some of them (sorry, it's gonna be loooooong, so perhaps I should post somewhere else as well). 1/40
First of all, "vendoring".

I see vendoring mentioned as "not the right solution" for dependency management. I agree that vendoring in itself was not the solution for dependency management, but this should be somewhat nuanced.

2/40
Vendoring is addressing multiple things, and go modules *can* address some of those.

So what does vendoring provide?

- reproducibility
- facilitate auditing source code
- guard against dependencies going AWOL (leftpad, y'all!)
- speed
- build in air gapped environments

3/40
Read 41 tweets
Jul 8, 2020
Completed surgery on this beauty. Power switch broke down, and (argh!) required a full dismantle.

Managed to repair the switch using contacts from a donor switch to replace the burned out ones.

Now close up the patient🤞🤞(this may take a while, *tons* of screws😞) ImageImage
"lots of screws" Image
Took the occasion to rinse the keyboard a bit (easier to access those nasty corners), and re-assembling actually wasn't horrible.

Was afraid that aligning the keyboard would be a challenge, but it snapped into place easily, and aligned with the screw hole first time! ImageImage
Read 6 tweets
May 12, 2020
Pro-top (and reminding myself) that in SemVer:

v1.0.0-rc10 < v1.0.0-rc2 < v1.0.0-rc9

whereas:

v1.0.0-rc.2 < v1.0.0-rc.9 < v1.0.0-rc.10
Both are valid SemVer, but have different meanings: the "pre-release suffix" (coming after "-") is a dot-separated identifier.

Without a dot, "rc9" and "rc10" are different pre-releases, so they are not compared numerically, but alphabetically
This usually works, e.g. "-alpha" comes before "-beta", comes before "-rc" when sorted alphabetically.

It also "works" when sorting numbers < 10, but after that things go wrong:

SemVer doesn't use natural sorting, so "1 < 10 < 2 < 20"
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(