apx doesn't detect subsystem after creating it

[pc-v2]

OS: Nobara 40
APX: 2.4.4
Container: docker (edit: also happens in podman)

Description:

• When I create a subsystems it returns distrobox enter apx-arch instead of apx arch enter.
• apx subsystems list didn't show any subsystems
• I use stacks from https://docs.vanillaos.org/apx/en/working-w-stacks

[taukakao]

I changed the title. Printing the distrobox command is just a visual problem and is to be expected. (It can be a separate issue but not finding the subsystem is much more severe so I'd prioritize that)

[jardon]

addressing the incorrect command being displayed, can you confirm which distrobox you are using?

[taukakao]

I think apx ships with distrobox

[jardon]

Yes, but there's no guarantee it's using that version on nobara

[taukakao]

It should be bundled with apx, not packaged.
But it's worth checking I guess.
Just make sure to check the bundled one, not the distros version.

[pc-v2]

I think apx ships with distrobox

I build it from github, so it does not come with distrobox it comes but I need to install separately

[pc-v2]

addressing the incorrect command being displayed, can you confirm which distrobox you are using?

[pc-v2]

I rebuild it with make all then install it, it does install distrobox, but I have to add to PATH in .bashrc to make it run, apx arch enter still does not work. I will recreate the container
edit, Apx still can't recognize the subsystems, it does recognized by distrobox

[pc-v2]

I reinstall apx with version 2.4.4 (release page), it does not come with distrobox, editing apx.json to locate the apx and distrobox, still broke.

Is this FS issue? I use btrfs by default

[taukakao]

apx is mainly used on VanillaOS, which uses btrfs as the default filesystem, so definitely not.

[taukakao]

Could you run
docker inspect apx-arch | jq '.[0].Config.Labels'
or if you don't have jq
docker inspect apx-arch | grep -C 15 "\"manager\""

[jardon]

a couple of things:

1. can you do a which distrobox? if its not the one included with apx then its likely a mismatch there
2. im assuming you did a recursive clone on the apx repo to pull in the distrobox submodule?

i think it can be confusing to troubleshoot if its not super clear which tool you are using. apx relies on labels of the containers to read the relevant subsystems from podman. if those arent in place or if they are mislabelled, apx wont find them

[pc-v2]

a couple of things:

1. can you do a `which distrobox`? if its not the one included with apx then its likely a mismatch there

2. im assuming you did a recursive clone on the apx repo to pull in the distrobox submodule?

i think it can be confusing to troubleshoot if its not super clear which tool you are using. apx relies on labels of the containers to read the relevant subsystems from podman. if those arent in place or if they are mislabelled, apx wont find them

I recloned it recursively yesterday

and I also uninstalling distrobox from package manager

this is now what it outputs

elgato ➜ ~/.../Dev-Repo/apx (main ✗) $ which distrobox
which: no distrobox in (/home/elgato/.local/bin/zen:/home/elgato/.local/bin/jellyfin:/home/elgato/.local/bin:/home/elgato/.deno/bin:/home/elgato/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin:/opt/rocm/hip/bin:/home/elgato/.cache/lm-studio/bin:/home/elgato/.spicetify:/home/elgato/.spicetify)
elgato ➜ ~/.../Dev-Repo/apx (main ✗) $ sudo which distrobox
which: no distrobox in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/var/lib/snapd/snap/bin)

[pc-v2]

Could you run docker inspect apx-arch | jq '.[0].Config.Labels' or if you don't have jq docker inspect apx-arch | grep -C 15 "\"manager\""

I almost give up and deleting apx-arch container, so instead I make ubuntu-noble subsystem to test if it also fail

elgato ➜ ~/.../Dev-Repo/apx (main ✗) $ docker inspect apx-ubuntu-noble | jq '.[0].Config.Labels'{
  "distrobox.unshare_groups": "0",
  "manager": "apx",
  "name": "ubuntu-noble",
  "nvidia": "true",
  "org.opencontainers.image.ref.name": "ubuntu",
  "org.opencontainers.image.version": "24.04",
  "stack": "ubuntu-noble-stacks"
}

elgato ➜ ~/.../Dev-Repo/apx (main ✗) $ apx ubuntu-noble enter
Error: unknown command "ubuntu-noble" for "apx"
Run 'apx --help' for usage.
  ERROR   unknown command "ubuntu-noble" for "apx"

[taukakao]

The tags look correct here so my hypothesis is out the window.