# Guix on Fedora Silverblue anyone? **URL:** \ **Category:** Guix\ **Created:** [May 30, 2026, 12:32am UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033 "2026-05-30T00:32:31Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![wegei8](https://avatars.discourse-cdn.com/v4/letter/w/53a042/32.png) [@wegei8](https://forum.systemcrafters.net/u/wegei8)\ **Post date:** [May 30, 2026, 12:32am UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/1 "2026-05-30T00:32:31Z")
Is anyone out there using Fedora Silverblue or any other immutable/atomic desktop with guix as a package manager? I’m currently trying out Silverblue and I mostly like it. The one huge drawback is that I can’t seem to install Guix on this thing. I found this: [Running guix package manager on top of Fedora Silverblue, updated instructions](https://sam-d.com/blog/running-guix-package-manager-on-top-of-fedora-silverblue-updated-instructions/) But it seems like a fragile way of running Guix that could break during any upgrade. I was trying myself with distrobox, but couldn’t get a successful `guix pull`. ```auto $ rpm-ostree override remove toolbox --install distrobox $ sudo mkdir -p /var/guix/gnu/store /var/guix/guix /var/guix/etc/guix $ distrobox create --name guix --image debian:13 --init --root \ --volume /var/guix/gnu/store:/gnu/store \ --volume /var/guix/guix:/var/guix \ --volume /var/guix/etc/guix:/etc/guix $ distrobox enter guix --root # etc... ``` ---
**Author:** ![trev](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.systemcrafters.net/trev/32/81_2.png) [@trev](https://forum.systemcrafters.net/u/trev)\ **Post date:** [May 30, 2026, 4:51am UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/2 "2026-05-30T04:51:45Z")
I was using this and had it working. Didn’t click the tutorial you linked, but here are my instructions and modified guix-daemon system service: > [Modified systemd service](https://github.com/trevarj/dotfiles/blob/master/systemd/.config/systemd/user/guix-daemon.service) ---
**Author:** ![wegei8](https://avatars.discourse-cdn.com/v4/letter/w/53a042/32.png) [@wegei8](https://forum.systemcrafters.net/u/wegei8)\ **Post date:** [June 4, 2026, 9:38pm UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/3 "2026-06-04T21:38:20Z")
Sweet toolbox approach. It would be nice not having to install another package… hm… I got the approach with distrobox working… it’s janky… but it seems like it’s working… The script ```auto $ cat install-guix-distrobox.sh #!/usr/bin/env bash set -e host_prefix=/var/guix set -x distrobox rm --root guix rm -f guix-install.sh sudo rm -rf $host_prefix sudo mkdir -p "$host_prefix/gnu/store" "$host_prefix/var/guix" "$host_prefix/etc/guix" "$host_prefix/var/log/guix" distrobox create --name guix --image debian:13 --init --root \ --additional-packages "uidmap netbase" \ --volume "$host_prefix/gnu/store:/gnu/store" \ --volume "$host_prefix/var/guix:/var/guix" \ --volume "$host_prefix/etc/guix:/etc/guix" \ --volume "$host_prefix/var/log/guix:/var/log/guix" curl -LO https://guix.gnu.org/guix-install.sh chmod u+x guix-install.sh distrobox enter --root guix -- sudo GUIX_ALLOW_OVERWRITE=1 ./guix-install.sh set +x echo "distrobox enter --root guix" echo "then" echo "sudo GUIX_ALLOW_OVERWRITE=1 ./guix-install.sh" ``` Using it ```auto host$ ./install-guix-distrobox.sh # the first run fails, is expected... host$ distrobox enter --root guix # yes, you have to re-run the installer guix$ sudo GUIX_ALLOW_OVERWRITE=1 ./guix-install.sh ``` It installs guix under `/var/guix` on the host. I believe this should survive container re-creation. With the toolbox approach, does the guix data get blown away if you have to re-create the container? ---
**Author:** ![trev](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.systemcrafters.net/trev/32/81_2.png) [@trev](https://forum.systemcrafters.net/u/trev)\ **Post date:** [June 10, 2026, 5:30am UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/4 "2026-06-10T05:30:19Z")
> [@wegei8](#): > > It would be nice not having to install another package What other package? Toolbox (`toolbx`) is built-in on Silverblue. Distrobox is a “beefed up” version of Toolbox. > [@wegei8](#): > > With the toolbox approach, does the guix data get blown away if you have to re-create the container? With toolbox or distrobox (they behave the same pretty much), removing the container will blow away the /gnu/store if you delete the container, so yes. ---
**Author:** ![16levels](https://avatars.discourse-cdn.com/v4/letter/1/cab0a1/32.png) [@16levels](https://forum.systemcrafters.net/u/16levels)\ **Post date:** [June 11, 2026, 11:48pm UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/5 "2026-06-11T23:48:42Z")
I’m late to the party, but I tried both a containerized `distrobox` approach and using `ostree-prepare-root` to add a `/gnu` mountpoint before deciding to create a custom bootc image. The `ostree-prepare-root` method was close, but broke `passt` networking for rootless containers. You can find my Containerfile here: [https://codeberg.org/16levels/guix-silverblue](https://codeberg.org/16levels/guix-silverblue) ---
**Author:** ![wegei8](https://avatars.discourse-cdn.com/v4/letter/w/53a042/32.png) [@wegei8](https://forum.systemcrafters.net/u/wegei8)\ **Post date:** [June 12, 2026, 5:30am UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/6 "2026-06-12T05:30:45Z")
> [@trev](#): > > What other package? Toolbox (`toolbx`) is built-in on Silverblue. Distrobox is a “beefed up” version of Toolbox. Sorry, I didn’t communicate clearly. I was complementing your toolbox approach because you didn’t have to `rpm-ostree install distrobox`, unlike me. That’s what I meant by “it would be nice not having to install another package”. > [@trev](#): > > With toolbox or distrobox (they behave the same pretty much), removing the container will blow away the /gnu/store if you delete the container, so yes. The distrobox approach is unaffected if you delete the container because I’m mounting host volumes into the container. I just ran `distrobox rm --root guix` and all of my data is still at `/var/guix`. ---
**Author:** ![wegei8](https://avatars.discourse-cdn.com/v4/letter/w/53a042/32.png) [@wegei8](https://forum.systemcrafters.net/u/wegei8)\ **Post date:** [June 12, 2026, 5:38am UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/7 "2026-06-12T05:38:52Z")
> [@16levels](#): > > [16levels/guix-silverblue: Fedora Silverblue bootc image with Guix package manager and Nvidia driver support. - Codeberg.org](https://codeberg.org/16levels/guix-silverblue) Ah, nice! I actually did stumble upon this during my research! Unfortunately, I haven’t had time to learn more about `bootc` and the customizations kinda scared me off (just cuz I don’t understand them). I was hoping for just vanilla Silverblue+Guix. Creating a custom OS image does seem to be the most correct way of doing it though. All of the other ways seem to have some odd drawbacks or issues. I need to find some more time to learn more about `bootc` and how all of that stuff works with Silverblue. Thanks! ---
**Author:** ![trev](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.systemcrafters.net/trev/32/81_2.png) [@trev](https://forum.systemcrafters.net/u/trev)\ **Post date:** [June 12, 2026, 5:49am UTC](https://forum.systemcrafters.net/t/guix-on-fedora-silverblue-anyone/2033/8 "2026-06-12T05:49:45Z")
wegei8 [notifications@systemcrafters.discoursemail.com](mailto:notifications@systemcrafters.discoursemail.com) writes: > The distrobox approach is unaffected if you delete the container > because I’m mounting host volumes into the container. I just ran > `distrobox rm --root guix` and all of my data is still at `/var/guix`. Ah ok, I get it now. Not sure if you can specify that with toolbx, but it does seem like a benefit. Did you try using two different distrobox containers against the same store?