This seems to be the way.

Short of weeding through the docs, I found the "Play with Kube using Podman" talk on DevConfs YouTube channel helpful.

I will be honest: that is even more confusing :)

> Note: The kube commands in podman focus on simplifying the process of moving containers from podman to a Kubernetes environment and from a Kubernetes environment back to podman.

I'll give it a try, but I'm starting to understand why there is so little use of podman among amateurs.

Personally, I am not interested in kubernetes, just podman for single-node use case. What the kube YAML does for this use case is provide a way to declare a multi-container application.

The podman documentation pages I have found most helpful for this use case are podman-kube-generate (generate kube YAML from an already running pod), podman-kube-play (run the kube manually) and podman-systemd.unit (run the kube as a service).

Edit: I should also mention that there are pod units (which don't require the use of kube YAML) but I skipped over them because they do not support podmans auto-update feature.

To reduce mouse hand travel I got a roller mouse pro slim about 6 months ago. Not great for fine motor tasks but exceptional for other general uses. Alleviated a lot of pain in my hands and fingers.

I use this with a small slim keychron keyboard and with a kinesis advantage 360.

The roller seems to be getting a bit sticky after 6 months of heavy use and transporting it between work and home. Nonetheless, would get another in a heartbeat.

Perhaps worth a look?

Roller mice are great. I also set up my keyboard such that I can hold down a key and use WASD to move my mouse, with J being left click and K being right. That's been a game changer for me, too.

I keep my Logitech MX close cause the infinite scroll is just too damn good. But the MX kills my hands when using for prolonged periods.

You right. This practice lives on in dubstep and soundsystem music in general.

I have also implemented it 3 times. Local updates from file system or USB and networked updates with the mongoose web page & the REST API. Quirky to configure when supporting all these methods at the same time but smooth and reliable once done.

Never got to implement a full OTA update system. SWUpdate supports suricatta & Siemens WFX for this. I played around with WFX and got OS updates working on my local network but didn't do anything else with it.

Nonetheless, if I wanted to implement my own OTA update solution swupdate & WFX seem like a beautiful combination.

If I may ask, how far did you take it?

I’ve only ever done hard connect updates over USB and manually pushed updates over local network. The team I was on was on track to switch over to pulled updates using Suricatta but I left before they switched them on.

Cool, thanks for sharing!

+1 for kas I won't build yocto images any other way. Using their kas-container script makes building with their container a breeze.

Other kas features I love: - Patching 3rd party layers with quilt - Configuration fragments - Chaining together configuration fragments

As another example, here is my kas setup for building rootfs images and container images for various different boards:

https://github.com/unitexe/meta-unit-kas

One has to implement the rollbacks in the bootloader after they have implemented an A/B update pattern.

In u-boot this is done with its boot count limit config and altbootcmd.