-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distrobox enter bazzite fails #288
Comments
I tried and it worked so must be something specific to the bazzite, bazzite-gnome and bazzite-deck images. |
More information based on --verbose from distrobox: [kheine@localhost-live ~]$ distrobox enter steam --verbose
++ date +%FT%T.%N%:z
DEBU[0000] Received: -1
|
Also see: ublue-os/bazzite-arch#16 |
Bazzite Arch is the image tailored for usage in distrobox. Other Bazzite images are meant to be installed on a system as you would a traditional operating system |
OK I found what the problem was with my setup. When I disable SELinux (boot selinux=0) then it fails but when I dont disable SELinux then the world is good. |
When trying to run bazzite through distrobox on Fedora 38 Workstation, I get the following error:
_[user@localhost-live bin]$ distrobox enter steam
Container steam is not running.
Starting container steam
run this command to follow along:
podman logs -f steam
Error: unable to start container "a4050f1e1e621228d454a6a84b14e9ec4ee83a162a7e908f1f5e95caccb630a6": crun: openat2
home
: No such file or directory: OCI runtime attempted to invoke a command that was not found_I have tried all the bazzite containers - bazzite-gnome bazzite-deck and they all have the same problem with :
crun: openat2
home
: No such file or directory: OCI runtime attempted to invoke a command that was not foundIs someone able to assist please as I love the idea of running a container image for each app to keep it container and in good running order.
Thanks and keep up the good work guys, I appreciate it.
The text was updated successfully, but these errors were encountered: