-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Subsystem based on Ubuntu stack fails to launch with either exit code 1 or 255 #386
Comments
I can't reproduce this. |
apx -v shows version 2.4.3 which is the latest, I think either there is a bug with apx that may cause this by not installing packages correctly while setting up the image or an issue with the ubuntu:latest image itself |
I can confirm this. I'm trying to setup a dev environment for my game project and I've created a special stack for that. I'm not sure if it just takes really really long or if it's actually crashing, because my other stack uses ubuntu:latest aswell, but works flawless. I guess that there's something wrong with a package or something. This is my stack config: I'm using the same packages on my Steam Deck where I've installed an ubuntu distrobox btw. |
ive tried to replicate this. I get a 255 error code despite the container starting. ive noticed that i do get a |
|
|
im wondering if youre getting the same error that I am. can you open a /.system/usr/share/apx/distrobox/distrobox ls
/.system/usr/share/apx/distrobox/distrobox enter --name <name-of-subsystem> |
Installing blender, mono and dotnet will take quite a lot of time. Apart from that, I don't think vscodium is a official ubuntu package. |
Can confirm, when i stop a container i am unable to start it up again. I get "Error OCI runtime error: crun: ptsname: Innapropriate ioctl for device Fresh install Vanilla OS 2 |
On a fresh installation of Vanilla OS 2, any apx subsystem created using the provided Ubuntu substack, which is based on the ubuntu:latest container image, fails to launch with either an exit code 255 or exit code 1 with the following error message:
Here, Test refers to the Ubuntu subsystem that I created. Resetting the subsystem and deletion does not seem to solve this issue. On the other hand using other stacks such as Fedora works normally, and I am able to install, update, run and remove packages without any issues.
The text was updated successfully, but these errors were encountered: