netplan VS containerd

For Netplan-based stuff, this looks similar:

* https://github.com/canonical/netplan/blob/main/examples/dire...

I recently had to switch ISPs to one that doesn't do IPv6 for FTTH (but their smart offerings are (AFAICT) IPv6-only), but my previous IPv6 did, and activating it for my home network was a couple clicks on my Asus router.

I'm not sure how far back you want to go, but you can install the ifupdown package and remove netplan.io. But, even in Ubuntu 16, they were starting to phase it out. So, you're going to hit some bugs here.

I was working with my Ubuntu 22.04 server and configuring my network with Netplan. After executing the Netplan apply command, I got an error message like the following:

Doesn't Ubuntu server use netplan.io by default?

The interfaces on omv are managed by netplan. https://netplan.io/

This is because Ubuntu Desktop uses NetworkManager to manage all the network interfaces by default. It is the application responsible for network management via UI. This is not the case in Ubuntu Server which I will be using. The documentation can be found here NetworkManager It can be completely turned off by choosing a different renderer or a specific networking interface can be excluded from under management of NetworkManager. The configuration is in the file /etc/NetworkManager/NetworkManager.conf. On UI less versions like Ubuntu Server there is no NetworkManager installed. The default network renderer is systemd-networkd. In both flavours of Ubuntu the networking configuration is done via Netplan and the configuration for Netplan is stored in yaml file in the location /etc/netplan/*.yaml. There could be more than one configuration file. More information on this are to be found in the provided link.

nautilus-extension-gnome-terminal nautilus-gtkhash nautilus-sendto nemo-fileroller neofetch net-tools netcat-openbsd netplan.io network-manager network-manager-config-connectivity-ubuntu network-manager-gnome

https://netplan.io/, yes?

Containerd and nerdctl

Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open Container Initiative or OCI's guidelines on container formats.

Container Engine: A runtime that executes and manages containers. Docker and containerd are popular container engines.

Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes.

This is a failed attempt to upstream part of containerd changes: https://github.com/containerd/containerd/pull/8789

Other part of containerd changes waits for gods-know-what: https://github.com/containerd/containerd/pull/9054

But I haven't gave up yet.

containerd is required by kubernetes to handle containers on its behalf. A big thanks to the HostAfrica blog for the information on setting containerd up for debain. So the containerd install will need to happen on both the WSL2 instance and the Raspberry Pis. For WSL2 you can just install containerd directly:

The context deadline exceeded: unknown is also in containerd, and is a known problem.

Get:1 https://download.docker.com/linux/ubuntu focal/stable amd64 containerd.io amd64 1.6.21-1 [28.3 MB]

Docker Desktop adds a bunch of stuff to simplify local development and that’s why it has a larger memory footprint. You don’t use that when deploying but something like https://containerd.io/.