@codingWombat Upstream with a tiny bit of layering 😅.

No seriously, I like the local rpm layering. I don't depend on a (self hosted) CI pipeline to deploy updates and I don't mind having that long list of layered packages. This is a pet server, it only exists once and is properly backed up.

#coreos

Today I learned: I don't need to put all my quadlets flat into containers/systemd, I can split them into subdirs 🎉.

That makes manually managing the ~50 containers (+volumes and networks) on my home server much clearer.

#podman #coreos #fedora #systemd

Fun fact: The best way to enable ptp_kvm on #coreos is ensuring the kernel arg ignition.platform.id=qemu is set. Then coreos-platform-chrony-config.service will load ptp_kvm and configure chrony accordingly.

rpm-ostree kargs --replace=ignition.platform.id=qemu

I was wondering why another VM at Ionos had ptp_kvm working without me setting it up. It turned out my Hetzner VM had ignition.platform.id=metal which prevents automatic ptp_kvm setup.

#hetzner #timekeeping #ntp #ptp #kvm #ionos

it lies or it is infinitely slow

#fedora #coreos #raspberrypi #cm4

Inspired by @bycx I started looking into CoreOS which seems like a good OS for my home cluster (immutable, more lightweight than Debian, easier to maintain).

I'm starting with a simple process - installing from flash drive and providing the installer with prepared Ignition config file (generated with Butane). The process went through but upon booting I get "unsupported config version". And indeed, the config doesn't validate with ignition-validate because. As simple as this is, I cannot make it work. What am I overlooking?

#CoreOS #Ignition #Butane

UniFi OS Server installs just fine on Fedora CoreOS when doing "rpm-ostree usroverlay" before starting the installer.

This will allow it to create symlinks in /usr/bin which are not needed and don't need to be persisted. Without temporarily enabling usroverlay the installer will leave UniFi OS Server in a broken state.

Coreos is a great match for UniFi OS because the base system will upgrade automatically while application upgrades are managed by UniFi.

#UniFi #fcos #fedora #coreos

Aaaand it won't. Of course it wants to write in places where it's not even sane to write to on a mutable OS.

#UniFi #fcos #fedora #coreos

If you have some #Fedora #CoreOS `testing` stream nodes check them to see if they have stuck updates. More info and workaround steps in https://lists.fedoraproject.org/archives/list/[email protected]/message/ZMWF2EBO5ZBJE53MJFD75YID7XTNEGMB/
[CoreOS] testing Stream: Zincati Upgrade Stall and Workaround - CoreOS - Fedora mailing-lists

I've been wrangling with #fedora #coreos since yesterday to setup a minimal forgejo runner instance running in #podman. Although I've been working with Flacar Linux (the successor to the original CoreOS) before, it seems to behave a little bit different here and there (e.g. SELinux).

I successfully installed CoreOS using an ignition file served by the python3 simple http server.

I suppose it's against the spirit of the #coreos platform to manually add password authentication to the SSHd config, but that's what I did. For reasons I don't understand my SSH public key didn't work.

That's an exercise for later. Next step is to see what I can do with #fibrechannel