Bazzite-Arch does not install during first setup

When trying to install Bazzite, going to the step of bazzite-arch, it errors out. i can just replicate it by running "just". Here is the output https://paste.centos.org/view/cca63c23
94 Replies
Tsubajashi (ツバジャシ)
(The german sentences are: "Datei oder Verzeichnis nicht gefunden" - "File or Directory not found")
dnkmmr
dnkmmr17mo ago
type podman logs -f bazzite-arch
Tsubajashi (ツバジャシ)
no output
dnkmmr
dnkmmr17mo ago
you should submit an issue for this on the github
Tsubajashi (ツバジャシ)
will do i guess
EyeCantCU
EyeCantCU17mo ago
If you run distrobox rm bazzite-arch and then just install-bazzite-arch what happens?
Tsubajashi (ツバジャシ)
cant even do that without any error seemingly
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox rm bazzite-arch
Do you really want to delete containers: bazzite-arch? [Y/n]: y
grep: /home/tsubajashi/.local/bin: Datei oder Verzeichnis nicht gefunden
bazzite-arch
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox rm bazzite-arch
Do you really want to delete containers: bazzite-arch? [Y/n]: y
grep: /home/tsubajashi/.local/bin: Datei oder Verzeichnis nicht gefunden
bazzite-arch
will continue anyway though same error as in aboves paste after running just install-bazzite-arch
EyeCantCU
EyeCantCU17mo ago
I'm sorry, I just know English and a little bit of Spanish and a smaller amount of German. What does that last part say?
Tsubajashi (ツバジャシ)
"File or Directory not found" sorry, i can change my stuff to english later on
EyeCantCU
EyeCantCU17mo ago
It's all right. I can always translate it
dnkmmr
dnkmmr17mo ago
try making another user and try to install bazzite-arch as another user. If it works on a different user, it is something to do with your user files. If it doesn't work on another user, it is something to do with the os itself
Tsubajashi (ツバジャシ)
will do, itll take a second though
Kyle Gospo
Kyle Gospo17mo ago
What's your base image?
Error: OCI runtime error: unable to start container "88cfbc4f78bd685ba816061236823746a2fe5dff4cfa7f6baecbe2586a67cbf9": crun: sethostname: Invalid argument
Error: OCI runtime error: unable to start container "88cfbc4f78bd685ba816061236823746a2fe5dff4cfa7f6baecbe2586a67cbf9": crun: sethostname: Invalid argument
never seen this before
EyeCantCU
EyeCantCU17mo ago
I highly doubt it does, but could this have anything to do with reintroducing toolbox? Aside from signing the image, that was the only thing I noticed in their ostree log
Tsubajashi (ツバジャシ)
same issue on the other user i used the 1.0.1 iso from github, then picked bazzite-nvidia
EyeCantCU
EyeCantCU17mo ago
What does rpm-ostree status say?
Kyle Gospo
Kyle Gospo17mo ago
this is something with distrobox/podman
Tsubajashi (ツバジャシ)
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ rpm-ostree status
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Digest: sha256:497c39f55e2f441beef6fec01a11b5a69afe66abccb59529882abf222c25831a
Version: 38.20230829.0 (2023-08-29T16:29:18Z)

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Digest: sha256:497c39f55e2f441beef6fec01a11b5a69afe66abccb59529882abf222c25831a
Version: 38.20230829.0 (2023-08-29T16:29:18Z)

ostree-unverified-image:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Digest: sha256:983c0205212551c924d971f4c80b1f9b5e39df71f461c6ba1f0291ea5668fffc
Version: 38.20230829.0 (2023-08-29T15:33:15Z)
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ rpm-ostree status
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Digest: sha256:497c39f55e2f441beef6fec01a11b5a69afe66abccb59529882abf222c25831a
Version: 38.20230829.0 (2023-08-29T16:29:18Z)

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Digest: sha256:497c39f55e2f441beef6fec01a11b5a69afe66abccb59529882abf222c25831a
Version: 38.20230829.0 (2023-08-29T16:29:18Z)

ostree-unverified-image:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Digest: sha256:983c0205212551c924d971f4c80b1f9b5e39df71f461c6ba1f0291ea5668fffc
Version: 38.20230829.0 (2023-08-29T15:33:15Z)
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$
Kyle Gospo
Kyle Gospo17mo ago
try making any distrobox distrobox create --name fedora --image fedora:latest distrobox enter fedora
EyeCantCU
EyeCantCU17mo ago
This is perfect
Tsubajashi (ツバジャシ)
takes a hot second, but i was able to create it. entering it, it wants to install packages aaand im inside the container
Kyle Gospo
Kyle Gospo17mo ago
that makes no sense
Tsubajashi (ツバジャシ)
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox create --name fedora --image fedora:latest
Image fedora:latest not found.
Do you want to pull the image now? [Y/n]: y
Resolved "fedora" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull registry.fedoraproject.org/fedora:latest...
Getting image source signatures
Copying blob 18ca996a454f done
Copying config 72c9e45642 done
Writing manifest to image destination
72c9e456423548988a55fa920bb35c194d568ca1959ffcc7316c02e2f60ea0ff
Creating 'fedora' using image fedora:latest [ OK ]
Distrobox 'fedora' successfully created.
To enter, run:

distrobox enter fedora

[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox enter fedora
Container fedora is not running.
Starting container fedora
run this command to follow along:

podman logs -f fedora

Starting container... [ OK ]
Installing basic packages... [ OK ]
Setting up read-only mounts... [ OK ]
Setting up read-write mounts... [ OK ]
Setting up host's sockets integration... [ OK ]
Integrating host's themes, icons, fonts... [ OK ]
Setting up package manager exceptions... [ OK ]
Setting up rpm exceptions... [ OK ]
Setting up sudo... [ OK ]
Setting up groups... [ OK ]
Setting up users... [ OK ]
Setting up groups... [ OK ]
Setting up users... [ OK ]
Executing init hooks... [ OK ]

Container Setup Complete!
📦[tsubajashi@fedora tsubajashi]$
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox create --name fedora --image fedora:latest
Image fedora:latest not found.
Do you want to pull the image now? [Y/n]: y
Resolved "fedora" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull registry.fedoraproject.org/fedora:latest...
Getting image source signatures
Copying blob 18ca996a454f done
Copying config 72c9e45642 done
Writing manifest to image destination
72c9e456423548988a55fa920bb35c194d568ca1959ffcc7316c02e2f60ea0ff
Creating 'fedora' using image fedora:latest [ OK ]
Distrobox 'fedora' successfully created.
To enter, run:

distrobox enter fedora

[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox enter fedora
Container fedora is not running.
Starting container fedora
run this command to follow along:

podman logs -f fedora

Starting container... [ OK ]
Installing basic packages... [ OK ]
Setting up read-only mounts... [ OK ]
Setting up read-write mounts... [ OK ]
Setting up host's sockets integration... [ OK ]
Integrating host's themes, icons, fonts... [ OK ]
Setting up package manager exceptions... [ OK ]
Setting up rpm exceptions... [ OK ]
Setting up sudo... [ OK ]
Setting up groups... [ OK ]
Setting up users... [ OK ]
Setting up groups... [ OK ]
Setting up users... [ OK ]
Executing init hooks... [ OK ]

Container Setup Complete!
📦[tsubajashi@fedora tsubajashi]$
Kyle Gospo
Kyle Gospo17mo ago
ok, let's clean you out distrobox stop bazzite-arch distrobox rm bazzite-arch
Tsubajashi (ツバジャシ)
cant rm it
Kyle Gospo
Kyle Gospo17mo ago
podman image rm bazzite-arch
Tsubajashi (ツバジャシ)
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox stop bazzite-arch Do you really want to stop bazzite-arch? [Y/n]: y bazzite-arch [tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox rm bazzite-arch Do you really want to delete containers: bazzite-arch? [Y/n]: y grep: /home/tsubajashi/.local/bin: Datei oder Verzeichnis nicht gefunden bazzite-arch
Kyle Gospo
Kyle Gospo17mo ago
you might have to keep stopping and rming it until it goes through
Tsubajashi (ツバジャシ)
it cant find something, i dont think that this is dynamic, or is it? but fair enough, whats the next step?
Kyle Gospo
Kyle Gospo17mo ago
if you did that podman image rm that means you have nothing left of your first attempt
Tsubajashi (ツバジャシ)
ive
podman image rm bazzite-arch
podman image rm bazzite-arch
it, its deleted
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ podman image rm bazzite-arch
Untagged: ghcr.io/ublue-os/bazzite-arch:latest
Deleted: 6a2343c20a85a9f78278f7ce0de8efb52a9c1a814cc0a07bdabd662633820d8b
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ podman image rm bazzite-arch
Untagged: ghcr.io/ublue-os/bazzite-arch:latest
Deleted: 6a2343c20a85a9f78278f7ce0de8efb52a9c1a814cc0a07bdabd662633820d8b
Kyle Gospo
Kyle Gospo17mo ago
distrobox create --name bazzite-arch --image ghcr.io/ublue-os/bazzite-arch distrobox enter bazzite-arch
EyeCantCU
EyeCantCU17mo ago
Also --nvidia
Kyle Gospo
Kyle Gospo17mo ago
oop yeah, add --nvidia to the create
Tsubajashi (ツバジャシ)
alrighty 😄 ah, so --nvidia allows distrobox/podman to use nvidia now? im so out of the loop there
Kyle Gospo
Kyle Gospo17mo ago
yep, loads the drivers from the host into the box cool stuff
Tsubajashi (ツバジャシ)
so podman can successfully use nvidia-container-toolkit too, right that would be so nice, i could use my docker image directly with podman then
Kyle Gospo
Kyle Gospo17mo ago
yep
Tsubajashi (ツバジャシ)
cant enter bazzite-arch
Kyle Gospo
Kyle Gospo17mo ago
same error?
Tsubajashi (ツバジャシ)
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox enter bazzite-arch
Container bazzite-arch is not running.
Starting container bazzite-arch
run this command to follow along:

podman logs -f bazzite-arch

Error: OCI runtime error: unable to start container "58c7927c57d1881fc1cda3c346c4d872065b5af15792640c228d14068e189f98": crun: sethostname: Invalid argument
[tsubajashi@p200300e3d70776b8dabbc1fffe68fcf7 tsubajashi]$ distrobox enter bazzite-arch
Container bazzite-arch is not running.
Starting container bazzite-arch
run this command to follow along:

podman logs -f bazzite-arch

Error: OCI runtime error: unable to start container "58c7927c57d1881fc1cda3c346c4d872065b5af15792640c228d14068e189f98": crun: sethostname: Invalid argument
yep
Kyle Gospo
Kyle Gospo17mo ago
how utterly bizzare
Tsubajashi (ツバジャシ)
indeed, especially since the fedora container works but that also means i wasnt too dumb installing it haha something else is wonky if i would have to guess, did you (or whoever maintains that container) change arguments for crun lately?
Kyle Gospo
Kyle Gospo17mo ago
nope pulling it down on my end right now
Tsubajashi (ツバジャシ)
awesome
Kyle Gospo
Kyle Gospo17mo ago
No description
Tsubajashi (ツバジャシ)
but so far, i just wanted to say: really nice project
Kyle Gospo
Kyle Gospo17mo ago
see if I can reproduce this
Tsubajashi (ツバジャシ)
ive played a bit of sonic robo blast 2 while letting it do its work, and it works perfectly
Kyle Gospo
Kyle Gospo17mo ago
No description
Tsubajashi (ツバジャシ)
so many ways to do something with containers, its awesome! whenever bazzite-arch works again, i gotta install xivlauncher-rb in it, since i assume it can use the AUR. then i can finally play my favorite game 😄
Kyle Gospo
Kyle Gospo17mo ago
working for me
Tsubajashi (ツバジャシ)
how weird
dnkmmr
dnkmmr17mo ago
glad it now works
Tsubajashi (ツバジャシ)
not for me (yet) still hitting the same error
dnkmmr
dnkmmr17mo ago
oh dang
Kyle Gospo
Kyle Gospo17mo ago
aye, aur works
Kyle Gospo
Kyle Gospo17mo ago
No description
Tsubajashi (ツバジャシ)
awesome!
Kyle Gospo
Kyle Gospo17mo ago
gonna check distrobox issue tracker see if anyone else has your issue doesn't appear to be our container
Tsubajashi (ツバジャシ)
how can i force an update? maybe that is enough, restarting, and seeing if the container then works?
Kyle Gospo
Kyle Gospo17mo ago
deleting the image in podman should have made it download the image 100% fresh if you mean the host OS rpm-ostree update
dnkmmr
dnkmmr17mo ago
if you are just using distrobox you can use the -p flag as well
Kyle Gospo
Kyle Gospo17mo ago
how long is your hostname?
Tsubajashi (ツバジャシ)
the default hostname the OS gave me p200300e3d70776b8dabbc1fffe68fcf7
Kyle Gospo
Kyle Gospo17mo ago
default should have been fedora I think what's happening is distrobox is attempting to add bazzite-arch to the hostname
Tsubajashi (ツバジャシ)
wasnt the case for me 😦
Kyle Gospo
Kyle Gospo17mo ago
andthe end result is too long
Tsubajashi (ツバジャシ)
how can i change it?
Kyle Gospo
Kyle Gospo17mo ago
change your hostname and try one more time for me this GNOME or KDE?
Tsubajashi (ツバジャシ)
KDE i much prefer KDE on a desktop, GNOME is something i like for laptops and tablets i changed the hostname with hostnamectl set-hostname to "tvp-desktop-bazzite" and it still makes that error
Error: OCI runtime error: unable to start container "58c7927c57d1881fc1cda3c346c4d872065b5af15792640c228d14068e189f98": crun: sethostname: Invalid argument
Error: OCI runtime error: unable to start container "58c7927c57d1881fc1cda3c346c4d872065b5af15792640c228d14068e189f98": crun: sethostname: Invalid argument
Kyle Gospo
Kyle Gospo17mo ago
you likely need to reboot and delete the box
Tsubajashi (ツバジャシ)
will do
Kyle Gospo
Kyle Gospo17mo ago
not sure what happened here just verified all of my VMs have fedora as the hostname my decks have "steamdeck" only because I changed it should be default behavior of upstream might have to add a safety check to the portal for this case to save someone a ton of time
Tsubajashi (ツバジャシ)
restarted, deleted the box and image, and will pull again yep, thats definitely needed. it already goes much further than before lets hope it completely passes everything it needs to do
Kyle Gospo
Kyle Gospo17mo ago
since you didn't do this from the portal once you're in, run this too:
Tsubajashi (ツバジャシ)
im in the container now, awesome
Kyle Gospo
Kyle Gospo17mo ago
distrobox-export --app steam distrobox-export --app lutris distrobox-export --app protontricks
mkdir -p ~/.steam && distrobox-export --bin /usr/bin/steamcmd --export-path ~/.steam && mv ~/.steam/steamcmd ~/.steam/steamcmd.sh
mkdir -p ~/.steam && distrobox-export --bin /usr/bin/steamcmd --export-path ~/.steam && mv ~/.steam/steamcmd ~/.steam/steamcmd.sh
that should be it
Tsubajashi (ツバジャシ)
yep, that did it seems to work now
Kyle Gospo
Kyle Gospo17mo ago
nice
Tsubajashi (ツバジャシ)
atleast, lutris runs, steam updates too havent tried protontricks yet but since both run, i assume it does work just to verify, if i install something inside the container, i have to always export it manually if i want it in my appmenu, right?
Kyle Gospo
Kyle Gospo17mo ago
that's right
EyeCantCU
EyeCantCU17mo ago
Yeah
Tsubajashi (ツバジャシ)
ok, nice i guess that was just an oopsie after install. i have never even typed in a hostname, so it made me some random long hostname
Kyle Gospo
Kyle Gospo17mo ago
wish we knew why but no matter, we can pop up a message about it in the future just in case
Tsubajashi (ツバジャシ)
i would install bazzite on my laptop aswell, maybe we find out why that happens there although, there i would run bazzite-gnome-nvidia
Eeyore_Syndrome
Eeyore_Syndrome16mo ago
I just tried to install bazzite-arch on a fresh bazzite-desktop install and a rebase from kinoite>bazzite-latest and same issue: - https://github.com/ublue-os/bazzite/issues/252 It will only let me install a fedora toolbox -.-
GitHub
bazzite arch image/ "invalid reference format/no such container". ·...
I tried with a fresh Bazzite install and the Bazzite-Portal/yafti just spit out error messages. I tried installing it with just and it errors out with: source /etc/default/bazzite && echo &...
Makaba
Makaba16mo ago
how did you solve this?
Kyle Gospo
Kyle Gospo16mo ago
what's your hostname?
Makaba
Makaba16mo ago
"fedora"
Kyle Gospo
Kyle Gospo16mo ago
and you're for sure getting crun: sethostname: Invalid argument? only time I've seen this it was a user with a hostname that was up to the character limit so distrobox couldn't append -bazzite-arch to the hostname like it nomally does
Makaba
Makaba16mo ago
Error: OCI runtime error: unable to start container "13e4314115109794ff89309b7826c594659512c391774a238499c236d68b09f0": crun: error `creating` systemd unit `libpod-13e4314115109794ff89309b7826c594659512c391774a238499c236d68b09f0.scope`: got `failed
Error: OCI runtime error: unable to start container "13e4314115109794ff89309b7826c594659512c391774a238499c236d68b09f0": crun: error `creating` systemd unit `libpod-13e4314115109794ff89309b7826c594659512c391774a238499c236d68b09f0.scope`: got `failed
Kyle Gospo
Kyle Gospo16mo ago
totally different issue never seen it before either, let me do some research
Want results from more Discord servers?
Add your server