#ostree — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ostree, aggregated by home.social.
-
Dear ostree users out there (on Fedora, RHEL, Bluefin, Aurora, Bazzite, ...),
has anyone of you ever seen an error regarding "invalid gzip headers" during a "rpm-ostree upgrade"?
[...]
[2/98] Fetching ostree chunk 53a115d85164231992f (46,2 MB)... done
error: Importing: Unencapsulating base: Layer sha256:53a115d85164231992fb38d82f836a36e9be489b15cfa415559419d164a7b6c0: Importing objects: invalid gzip headerI am building my own images to have the /nix directory available. Worked like a charm but suddenly stopped working for my Fedora43 image due to this error. The Aurora-with-nix image is fine, though.
Funnily enough, as my image only adds the nix directory, I only have one "custom" layer, everything else is from the upstream image. So I am puzzled on why this fails, why it fails for me and not for anybody/everybody else and why I do not find any issues related to "invalid gzip header" errors...
#Fedora #OSTree #rpm-ostree #Aurora #Linux #immutable #HellYeah #DevOps
-
Dear ostree users out there (on Fedora, RHEL, Bluefin, Aurora, Bazzite, ...),
has anyone of you ever seen an error regarding "invalid gzip headers" during a "rpm-ostree upgrade"?
[...]
[2/98] Fetching ostree chunk 53a115d85164231992f (46,2 MB)... done
error: Importing: Unencapsulating base: Layer sha256:53a115d85164231992fb38d82f836a36e9be489b15cfa415559419d164a7b6c0: Importing objects: invalid gzip headerI am building my own images to have the /nix directory available. Worked like a charm but suddenly stopped working for my Fedora43 image due to this error. The Aurora-with-nix image is fine, though.
Funnily enough, as my image only adds the nix directory, I only have one "custom" layer, everything else is from the upstream image. So I am puzzled on why this fails, why it fails for me and not for anybody/everybody else and why I do not find any issues related to "invalid gzip header" errors...
#Fedora #OSTree #rpm-ostree #Aurora #Linux #immutable #HellYeah #DevOps
-
Dear ostree users out there (on Fedora, RHEL, Bluefin, Aurora, Bazzite, ...),
has anyone of you ever seen an error regarding "invalid gzip headers" during a "rpm-ostree upgrade"?
[...]
[2/98] Fetching ostree chunk 53a115d85164231992f (46,2 MB)... done
error: Importing: Unencapsulating base: Layer sha256:53a115d85164231992fb38d82f836a36e9be489b15cfa415559419d164a7b6c0: Importing objects: invalid gzip headerI am building my own images to have the /nix directory available. Worked like a charm but suddenly stopped working for my Fedora43 image due to this error. The Aurora-with-nix image is fine, though.
Funnily enough, as my image only adds the nix directory, I only have one "custom" layer, everything else is from the upstream image. So I am puzzled on why this fails, why it fails for me and not for anybody/everybody else and why I do not find any issues related to "invalid gzip header" errors...
#Fedora #OSTree #rpm-ostree #Aurora #Linux #immutable #HellYeah #DevOps
-
Dear ostree users out there (on Fedora, RHEL, Bluefin, Aurora, Bazzite, ...),
has anyone of you ever seen an error regarding "invalid gzip headers" during a "rpm-ostree upgrade"?
[...]
[2/98] Fetching ostree chunk 53a115d85164231992f (46,2 MB)... done
error: Importing: Unencapsulating base: Layer sha256:53a115d85164231992fb38d82f836a36e9be489b15cfa415559419d164a7b6c0: Importing objects: invalid gzip headerI am building my own images to have the /nix directory available. Worked like a charm but suddenly stopped working for my Fedora43 image due to this error. The Aurora-with-nix image is fine, though.
Funnily enough, as my image only adds the nix directory, I only have one "custom" layer, everything else is from the upstream image. So I am puzzled on why this fails, why it fails for me and not for anybody/everybody else and why I do not find any issues related to "invalid gzip header" errors...
#Fedora #OSTree #rpm-ostree #Aurora #Linux #immutable #HellYeah #DevOps
-
Dear ostree users out there (on Fedora, RHEL, Bluefin, Aurora, Bazzite, ...),
has anyone of you ever seen an error regarding "invalid gzip headers" during a "rpm-ostree upgrade"?
[...]
[2/98] Fetching ostree chunk 53a115d85164231992f (46,2 MB)... done
error: Importing: Unencapsulating base: Layer sha256:53a115d85164231992fb38d82f836a36e9be489b15cfa415559419d164a7b6c0: Importing objects: invalid gzip headerI am building my own images to have the /nix directory available. Worked like a charm but suddenly stopped working for my Fedora43 image due to this error. The Aurora-with-nix image is fine, though.
Funnily enough, as my image only adds the nix directory, I only have one "custom" layer, everything else is from the upstream image. So I am puzzled on why this fails, why it fails for me and not for anybody/everybody else and why I do not find any issues related to "invalid gzip header" errors...
#Fedora #OSTree #rpm-ostree #Aurora #Linux #immutable #HellYeah #DevOps
-
🐧Bootc and OSTree: Modernizing Linux System Deployment
｢ OSTree is often described as “Git for filesystems”. It enables versioning, distribution, and atomic deployment of Linux systems. Rather than managing packages individually, OSTree stores complete system snapshots, making updates and rollbacks easier ｣
#boot #ostree #opensource #linux
https://a-cup-of.coffee/blog/ostree-bootc/ -
Bootc and OSTree: Modernizing Linux System Deployment
-
Esta es la realidad de #flatpak al actualizar: un par de megas o menos. Si el cambio es pequeño no hace falta "reempaquetar" todo y bajarlo entero. Por eso a #OSTree se le conoce como el git de los binarios.
Flatpak te sale a cuentas, por espacio, si usas todas las aplicaciones. Para una o dos no te vale la pena instalar tres o cuatro tiempos de ejecución.
-
OSTree без магии: атомарные обновления, репозиторий и клиентский образ своими руками
На Хабре про OSTree обычно вспоминают не как про самостоятельную технологию, а как про "то, на чём держатся" Fedora CoreOS / Silverblue / Kinoite и вообще вся тема immutable / atomic desktop / container-optimized OS . Это видно по типовым материалам: обзор CoreOS с объяснением rpm-ostree и layering, обзор Silverblue, новости/разборы релизов Fedora, где rpm-ostree фигурирует как механизм поставки базовой системы. При этом намного хуже покрыта практическая сторона "как сделать свой цикл поставки" : поднять свой OSTree-репозиторий, выпускать свои refs и раскатывать их на узлы так, чтобы можно было обновиться и откатиться , а не как герои трагикомедии "обновили пакеты — и внезапно утро не наступило". На фоне обилия статей "как устроен Silverblue/CoreOS" такой сценарий встречается реже. Мы раскроем полный цикл от публикации сервера до создания клиентских образов в этой статье.
-
ARCH LINUX BOOTC WORKS. I DECLARE THE LINUX ATOMIC AGE IS UPON US!
-
and here it is, after asking on the #Kinoite matrix channel dev Tim Ravier pointed me here https://pagure.io/releng/failed-composes/issues
and logs https://kojipkgs.fedoraproject.org/compose/updates/
Useful to see what is appearing in testing composes and when and why your testing branch box hasn't received anything in weeks 😆
#fedora #ostree #compose #fedoraatomic #kinoite #silverblue #linux
-
Fedora OSTree: Update & NVIDIA
Fedora OSTree mit NVIDIA proprietären Treiber Release Update. RPMFusion Abhängigkeit zur Version auflösen
-
Fedora OSTree: Update & NVIDIA
Fedora OSTree mit NVIDIA proprietären Treiber Release Update. RPMFusion Abhängigkeit zur Version auflösen
-
Fedora OSTree: Update & NVIDIA
Fedora OSTree mit NVIDIA proprietären Treiber Release Update. RPMFusion Abhängigkeit zur Version auflösen
-
Fedora OSTree: Update & NVIDIA
Fedora OSTree mit NVIDIA proprietären Treiber Release Update. RPMFusion Abhängigkeit zur Version auflösen
-
Fedora OSTree: Update & NVIDIA
Fedora OSTree mit NVIDIA proprietären Treiber Release Update. RPMFusion Abhängigkeit zur Version auflösen
-
If you are a maintainer of #nix, #nixpkgs or #nixos: listen up.
You've got about 2 years or so being a serious contender, until someone like #lix or even #ostree with #ComposeFS comes in and eats your lunch.
Part and parcel of that is the community, the language, the security of knowing that there is culpability and responsibility.
Linus Torvalds had to walk it off because an entire foundation told him to. If the nix "community" is beyond this, why give #DeterminateSystems contracts?
-
So... instead of going back to #FedoraAtomic, I'm going over to... #lix. Well tomorrow I'm going over to.
I'm on #NixOS now and the idea of going from #nix to lix intrigues me. It's just a change of the underlying tooling that interacts with the nix store, but I'm fascinated by the idea that you can compose NixOS using whatever tooling that works with it.
The nix store is then fully decoupled from nix and nixpkgs, making it more a competing standard against #ostree.
-
Fedora Silverblue — мнение с точки зрения джависта
Привет, меня зовут Егор Гаврилов, и я хочу рассказать о Fedora Silverblue с точки зрения Junior Java Developer'а, который использует данный дистрибутив в качестве повседневной ОС.
-
Fedora Silverblue — мнение с точки зрения джависта
Привет, меня зовут Егор Гаврилов, и я хочу рассказать о Fedora Silverblue с точки зрения Junior Java Developer'а, который использует данный дистрибутив в качестве повседневной ОС.
-
Ok, am I weird or does this make no sense? To pin an #ostree deployment in #fedora #atomic desktop you use e.g.
sudo ostree* admin pin 0
Naively, I always think it should be
sudo ostree admin unpin 0
to unpin it again. But no. My sweat summer child. Why, it's *obviously*:
sudo ostree admin pin --unpin 0
(I kinda get why it is that but I will never be able to remember that.)
*Why not rpm-ostree? So many questions.
-
Ok, am I weird or does this make no sense? To pin an #ostree deployment in #fedora #atomic desktop you use e.g.
sudo ostree* admin pin 0
Naively, I always think it should be
sudo ostree admin unpin 0
to unpin it again. But no. My sweat summer child. Why, it's *obviously*:
sudo ostree admin pin --unpin 0
(I kinda get why it is that but I will never be able to remember that.)
*Why not rpm-ostree? So many questions.
-
Ok, am I weird or does this make no sense? To pin an #ostree deployment in #fedora #atomic desktop you use e.g.
sudo ostree* admin pin 0
Naively, I always think it should be
sudo ostree admin unpin 0
to unpin it again. But no. My sweat summer child. Why, it's *obviously*:
sudo ostree admin pin --unpin 0
(I kinda get why it is that but I will never be able to remember that.)
*Why not rpm-ostree? So many questions.
-
Ok, am I weird or does this make no sense? To pin an #ostree deployment in #fedora #atomic desktop you use e.g.
sudo ostree* admin pin 0
Naively, I always think it should be
sudo ostree admin unpin 0
to unpin it again. But no. My sweat summer child. Why, it's *obviously*:
sudo ostree admin pin --unpin 0
(I kinda get why it is that but I will never be able to remember that.)
*Why not rpm-ostree? So many questions.
-
Ok, am I weird or does this make no sense? To pin an #ostree deployment in #fedora #atomic desktop you use e.g.
sudo ostree* admin pin 0
Naively, I always think it should be
sudo ostree admin unpin 0
to unpin it again. But no. My sweat summer child. Why, it's *obviously*:
sudo ostree admin pin --unpin 0
(I kinda get why it is that but I will never be able to remember that.)
*Why not rpm-ostree? So many questions.
-
I don't know who needs to hear this, but #System76 needs to rebase #PopOS. No shot, the current stable is 22.04... 22... 04.
#Ubuntu #Linux cannot be trusted, because snaps - and Shuttleworth - which means they have to go fully #Debian, which is respectable, but hear me out here...
I can hear you booing from the back, and I can feel the glee of @BrodieOnLinux , but even though I like #Fedora I think competition is good and that #uBlue has that vector sown up. Also, #IBM.
-
#Fedora really tipped #Ubuntu from its perch, and #uBlue as well as #Bazzite are examples of that.
Don't get me wrong, #Mint and even #Arch are still the everyman distros, but point me to another #libre distribution that has pushed the envelope as much as Fedora has.
#Nouveau, #Wayland, #PipeWire, #Ostree, etc. When it comes to #Linux, Fedora is a technology leader, and its users & organizational governance is key to that success.
Fedora Linux Turns Over A New Leaf
https://youtube.com/watch?v=4DyBUC0jIGE&si=OZLR_qWr8cL0MVG0 -
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
So I update my system's flatpaks only to discover that my flatpak build of visual studio no longer works with my flatpak tool for podman remote.
I'm at a bit of a loss here. I think I might just layer vscode into my podman image for now to avoid these types of issues, but I would honestly prefer to no have these types of things layered into my system.
-
does anyone know if bazzite:testing tracks the fedora updates-testing repo? Or is it just testing new changes to the bazzite tweaks?
#bazzite #fedora #updates #testing #universalblue #ostree #bugsinmesa
-
@ghastrum to me, something like Atomic is perfect for the general consumer.
Not only does it use isolated read-only system images (requiring reboot), but since it's #ostree you can easily swap remote refs, and rebase a system, which is preferable to massive uninstall and reinstall operations on a running system.
Think trying out Kinoite (#Plasma) instead of Silverblue (#GNOME). Sure, both dnf and apt can handle massive reinstalls, but the cruftification is real.
`rpm-ostree rebase` go brrr.
-
The recent @Cockpit release 314 fixes a security issue on the sos report page, improves read-only file systems, and shows container deployments in OSTree.
-
Fedora Ostree gamers, do you install steam as a flatpak, toolbox/distrobox container or layer it?
#silverblue #kinoite #fedora #sericea #vauxite #onyx #steam #linuxgaming #ostree
-
(For those of you who might not know, Fedora Silverblue is based on rpm-ostree.
Think of it as your OS on git.
Upgrades are like a simple git pull and take almost no time at all, even between major versions. It’s very common that I’m running today’s OS on my machine.
And if something goes wrong, you can always roll back. Not that I’ve had to yet.)
