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
(The german sentences are: "Datei oder Verzeichnis nicht gefunden" - "File or Directory not found")
type
podman logs -f bazzite-arch
no output
you should submit an issue for this on the github
will do i guess
If you run
distrobox rm bazzite-arch
and then just install-bazzite-arch
what happens?cant even do that without any error seemingly
will continue anyway though
same error as in aboves paste after running just install-bazzite-arch
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?
"File or Directory not found"
sorry, i can change my stuff to english later on
It's all right. I can always translate it
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
will do, itll take a second though
What's your base image?
never seen this before
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
same issue on the other user
i used the 1.0.1 iso from github, then picked bazzite-nvidia
What does rpm-ostree status say?
this is something with distrobox/podman
try making any distrobox
distrobox create --name fedora --image fedora:latest
distrobox enter fedora
This is perfect
takes a hot second, but i was able to create it. entering it, it wants to install packages
aaand im inside the container
that makes no sense
ok, let's clean you out
distrobox stop bazzite-arch
distrobox rm bazzite-arch
cant rm it
podman image rm bazzite-arch
[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
you might have to keep stopping and rming it
until it goes through
it cant find something, i dont think that this is dynamic, or is it?
but fair enough, whats the next step?
if you did that podman image rm
that means you have nothing left of your first attempt
ive it, its deleted
distrobox create --name bazzite-arch --image ghcr.io/ublue-os/bazzite-arch
distrobox enter bazzite-arch
Also --nvidia
oop yeah, add --nvidia to the create
alrighty 😄
ah, so --nvidia allows distrobox/podman to use nvidia now?
im so out of the loop there
yep, loads the drivers from the host into the box
cool stuff
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
yep
cant enter bazzite-arch
same error?
yep
how utterly bizzare
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?
nope
pulling it down on my end right now
awesome
but so far, i just wanted to say: really nice project
see if I can reproduce this
ive played a bit of sonic robo blast 2 while letting it do its work, and it works perfectly
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 😄
working for me
how weird
glad it now works
not for me (yet)
still hitting the same error
oh dang
aye, aur works
awesome!
gonna check distrobox issue tracker
see if anyone else has your issue
doesn't appear to be our container
how can i force an update? maybe that is enough, restarting, and seeing if the container then works?
deleting the image in podman should have made it download the image 100% fresh
if you mean the host OS
rpm-ostree update
if you are just using distrobox you can use the
-p
flag as wellhow long is your hostname?
the default hostname the OS gave me
p200300e3d70776b8dabbc1fffe68fcf7
default should have been
fedora
I think what's happening is distrobox is attempting to add bazzite-arch to the hostnamewasnt the case for me 😦
andthe end result is too long
how can i change it?
change your hostname and try one more time for me
this GNOME or KDE?
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
you likely need to reboot
and delete the box
will do
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
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
since you didn't do this from the portal
once you're in, run this too:
im in the container now, awesome
distrobox-export --app steam
distrobox-export --app lutris
distrobox-export --app protontricks
that should be ityep, that did it
seems to work now
nice
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?
that's right
Yeah
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
wish we knew why
but no matter, we can pop up a message about it in the future
just in case
i would install bazzite on my laptop aswell, maybe we find out why that happens there
although, there i would run bazzite-gnome-nvidia
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 &...
how did you solve this?
what's your hostname?
"fedora"
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
totally different issue
never seen it before either, let me do some research