Fedora had released Fedora CoreOS 43.20260413.3.2 on "stable stream" few hours ago to patch against Copy Fail.

Upgraded packages:

  • kernel-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
  • kernel-core-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
  • kernel-modules-6.19.11-- 200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
  • kernel-modules-core-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64

You can wait your zincati service schedule to upgrade automatically, or you can run sudo zincati-update-now to upgrade immediately.

#copyfail #fedora #fcos #coreos

Rolling-out zincati-update-now to update our Fedora CoreOS instances immediately and tackle copyfail.

#copyfail #fedora #coreos #fcos #zincati

@ercanbrack I can confirm this. Checked on my #Fedora 43 workstation.

But I'm still waiting for the next update of Fedora #CoreOS / #fcos.

Instance-instance fediverse "sangeunahna.com" untuk beberapa hari kemungkinan bakal sering restart. Efek dari pakai distro immutable/atomic Fedora CoreOS (FCOS), di awal-awal bakal sering restart karena setiap install sesuatu (yang non container) ya restart dulu biar image nya aktif.

Tapi enaknya nanti kalo dah matang, bisa dicuekin dia aman auto-update nya andalin zincati. Bahkan ketika FCOS keluarin major release baru. Pengalaman sudah berapa kali auto-upgrade major release server-server kami aman sentosa. Insya Allah gak akan pusing kalau versi pas install dah EOL.

#fedora #fcos #linux

Looks like I'm gonna exclude most of our #FCOS VMs from daily Proxmox #Backup Server.

Those FCOS VMs tasks are running containers. All we need is just backup quadlet files and /etc/default. For most of container's data, I think we can use application level replication. If it's not available, I rather backup those container's volumes.

Why?

Because full backup of vm disk images is too expensive. Not talking about storage price, but about extraneous load on infrastructures (cpu, storage i/o).

Fedora CoreOS Stable v43.20260316.3.1 has been released few hours ago with 49 packages upgraded, including kernel upgrade from 6.18.13 to 6.19.7.

https://www.fedoraproject.org/coreos

#fcos #fedora #linux

The container optimized OS

A minimal OS with automatic updates. Scalable and secure.

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

"UniFi OS Server" is the successor to #UniFi Network Application.

Is actually not a OS but supposedly a collection of podman containers and scripts that fuck around in the base OS as it pleases. 👀

Will this work in a dedicated #fcos VM? I'll find out.

Fedora CoreOS Release Notes

See the major changes and components version for latest Fedora CoreOS releases.