RPM OSTree Failure When Layering Steam Atop Vauxite

[kayomn]

When attempting to layer Steam onto the Vauxite image I get the following error during the staging:

error: Checkout libstdc++-14.2.1-1.fc40.i686: Hardlinking ac/859321dfe787f24d016e20e585da522713d84edbf0f6fb4e021543ece37264.file to __init__.cpython-312.opt-1.pyc: File exists

This is the output of my rpm-ostree status.

● ostree-unverified-image:docker://ghcr.io/ublue-os/vauxite-main:latest
                   Digest: sha256:8d721294a131a562968999d9e2de5457a7bf9fe2d334edc3f407f26a3ccdde2c
                  Version: 40.20240810.0 (2024-08-10T03:13:28Z)
          LayeredPackages: gvfs-smb

Note that the issue persists even after a full rpm-ostree reset, so I do not believe this to be specific to the package I have currently layered. I expect this is also happening with any fresh Vauxite image.

[xynydev]

Layering Steam is a pretty hard problem with rpm-ostree currently. Bazzite does it, and it works pretty well, but requires some hacks.

If you just want to install it locally and don't want to use Bazzite, I recommend against layering. The Flatpak and bazzite-arch are viable alternatives.

[kayomn]

I have encountered a few issues with the Steam flatpak, namely that it doesn't seem to detect devices too well and VR does not work at all.

I am looking into this as an alternative - are these hacks that Bazzite had to perform as a work-around documented anywhere?

[xynydev]

I'm not aware of there being much documentation. This is the RUN step that installs Steam for Bazzite (among other things): https://github.com/ublue-os/bazzite/blob/main/Containerfile#L421

If you really want to layer Steam, doing it locally will be even more of a headache.

[l33tllama]

Sadly this is the reason I have to use another distro, as the Steam SDK doesn't seem to work in games outside of Steam (game development) with the Steam flatpak..

[RoyalOughtness]

FYI with negativo, I've had better luck with local layering so far