roadmap VS k3s

x86-64 containers?

https://github.com/docker/roadmap/issues/384 is still open. :(

Request features or give feedback: https://github.com/docker/roadmap/issues/524

Nothing in the road map [Github] returned by searching 'stop'.

Further reading online revealed that host network mode is not available for swarm started with docker stack deploy. (Possible related open issue: github link).

Single-click k8s install. Extensions. Init. And there are people who just prefer an app-based experience for their own reasons - I think it was the most "upvoted" request ever on their public roadmap.

In case you need to run x86 containers: Docker has Rosetta support now but it's buggy.

https://github.com/docker/roadmap/issues/384

Without Rosetta it uses relatively slow Qemu emulation.

https://github.com/docker/roadmap/issues/44

So, at the moment, any public organization images are doomed to be lost, if they won't pay.

I've been watching this GitHub issue for damn near 3 years. Filesystem performance is pretty bad, depending on what you're doing. I had to kludge together workarounds to my DX at my last role where we used Docker for development. It was really, really painful and distracting.

[2] https://github.com/docker/roadmap/issues/7

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable.

Yes it’s going to depend on which k8s distribution you’re using. We have work in-progress for k3s to natively support nix-snapshotter: https://github.com/k3s-io/k3s/pull/9319

For other distributions, nix-snapshotter works with official containerd releases so it’s just a matter of toml configuration and a systemd unit for nix-snapshotter.

We run Kubernetes outside of NixOS, but yes the NixOS modules provided by the nix-snapshotter certainly make it simple.

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Kubernetes - k3s distribution

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later.

You should be familiar with Kubernetes and have set up a Kubernetes cluster. I recommend k3s.

K3s' go.mod[0] is insane.

[0] https://github.com/k3s-io/k3s/blob/master/go.mod