Well, had my first experience with Fedora #CoreOS :coreos: doing rpm-ostree updates automatically.
It would have been fine if it wasn't in the middle of the day when both the wife and I are gaming 😁
Fortunately Zincati has update strategies you can apply via file-based configuration, so gonna sort it so it does daily updates at a more sensible time like 5am. Just wasn't expecting the default to be YOLO.
Currently #Hetzner Cloud does not natively support #CoreOS (yet?).
So I created this #Packer template which lets you create an image. It even supports Ignition config via user data and automatic SSH public key and hostname configuration!
Have a look: https://github.com/mhutter/hcloud-packer-coreos
#hetzner #coreos #packer #hcloud
It took me a lot of debugging, a night staying up until 0530, and admitting to myself that it might not be entirely realistic for 100% of my server setup to be automated through Butane from the start.
But I finally did it. I now have a #Fedora #CoreOS installation 🥳 Only shortcut I took was disabling the abomination called SELinux.
Still have a lot to do I want to do though! Need to tinker with nvidia docker, set up Jellyfin, and try to securely automate samba setup.
Wow I was not expecting the drive I plugged in to be a @Solus :solus: 1.2.1 install from October 2016!
Doing some prep work to have #Fedora #CoreOS go on my home server, so was plugging in drives to check their contents, wipe if needed, etc. before getting to work on Ignite config via Butane. Had an old 500GB I was expecting to be maybe some Nextcloud files or similar.
Nope, content (and drive) clearly much older and uhhh...certainly will stay as a museum piece instead of getting wiped.
@nova would have loved this. The Spirit of #coreos lives on... or will... or something... with #webassembly..... at #wasmcon: https://sched.co/1PCLu.
@rm4 about 20 years ...it became a #hobby in #college when i was bored with my #business homework and #filesharing became limited in scope, for me ... a car wreck that broke my skull sophomore year really helped give me free time to learn ...it became my #career and i'm obsessed with it to this day #silverblue #voidlinux #alpinelinux #coreos #debian
#hobby #college #business #filesharing #career #silverblue #voidlinux #alpinelinux #coreos #Debian #Linux
Are you making a video or a podcast about Fedora Silverblue, Kinoite, Sericea, Onyx, IoT or CoreOS ? Feel free to reach out on the Fedora discussion forum! We can help you figure out issues or answer questions you may have with those "new" variants.
If you prefer, you can also reach out directly to me. You might also want to reach out to @jorge (Universal Blue) or @sfalken (openSUSE MicroOS, Aeon, Kalpa).
#Fedora #silverblue #Kinoite #coreos #IOT #universalblue
I need to leave this #server in an #error state until I create a proper method of alerting me when this particular problem happens again .... Day by day, its latest backup is becoming more stale ....I need to restore said #backup, eventually .... #telegraf in a #container has limited ability to transmit host #stats and I'm not finding a satisfying #solution because I don't want to #rpmostree install anything *especially* from some #dirty third party repo :ablobspin:
#server #error #backup #telegraf #container #stats #solution #rpmostree #dirty #tickstack #coreos #podman
I've written a post about how to setup libvirt on rpm-ostree systems (Fedora Silverblue, Kinoite, Sericea, Onyx, CoreOS) to get a more reasonable set of overlayed packages: https://discussion.fedoraproject.org/t/overlaying-libvirt-on-silverblue-kinoite-sericea-onyx-and-coreos/86312
Feedback and help to improve the situation welcomed!
#Fedora #silverblue #Kinoite #coreos
Do we need telemetry? What would it be used for? What kind of useful and non-personal data could we gather?
To try to answer those questions, I wrote a list of examples where telemetry would have been useful for Fedora CoreOS, Silverblue or Kinoite systems: https://discussion.fedoraproject.org/t/what-data-will-be-collected-exactly-a-breakout-topic-for-the-f40-change-request-on-privacy-preserving-telemetry-for-fedora-workstation/85417/47
#Kinoite #fedorachange #coreos #silverblue #Fedora
today:
* back from PTO, catching up with about a zillion emails and...you know...controversies
* tweaked the emergency fix tflink did for the #fedora #openqa scheduler while I was away - https://pagure.io/fedora-qa/fedora_openqa/c/fecd38f55c54056102a497edcff0cfa895580ed6?branch=main
* looked into Rawhide update test failures, seems to be a mess with qt6 rebuilds, waiting for @jgrulich to take care of it
* wrote a long explanation of why updates need 90 mins - 2 hours to be gated: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/J43SD7WXUQPTBUC742HE5M23BLHCJCB6/
* merged #coreos criteria changes - https://github.com/coreos/fedora-coreos-tracker/issues/1239
After writing up my Ghost blog deployment in containers on #fedora #coreos last week, I figured it was time for another post about how to put a #cdn in front of the site. 🐇
This one is a bit lengthy but adding a CDN to nearly anything is fairly complicated. 🥵
#fedora #coreos #cdn #aws #cloudfront #ghost #blog
Ten years ago today, #CoreOS Container Linux was born. As they say, “time flies when you’re having fun building secure infrastructure at scale”!
Had anyone every done any A/B boot partition testing with #Fedora #CoreOS? Might now the biggest issue I have with CoreOS right now is that every time I want to update the system confit I should update the ign file and basically reinstall the system. But I can’t really do that remotely at the moment.
If I can set up a good A/B I can reinstall B from A and then ignition sets eveything up the way it should be. Any real data saved on another partition of course.
Check out this post on CoreOS Layering by Mark Russell and @cgwalters https://cloud.redhat.com/blog/introducing-red-hat-enterprise-linux-coreos-layering #coreos #openshift