Cannot enter toolbox. chdir: No such file or directory: OCI runtime command not found error

Project Discussion
1 
toolbox -v create 
toolbox: running as real user ID 1002
toolbox: resolved absolute path for /usr/bin/toolbox to /usr/bin/toolbox
toolbox: checking if /etc/subgid and /etc/subuid have entries for user bruno2
toolbox: TOOLBOX_PATH is /usr/bin/toolbox
toolbox: running on a cgroups v2 host
toolbox: current Podman version is 1.8.2
toolbox: migration not needed: Podman version 1.8.2 is unchanged
toolbox: Fedora generational core is f32
toolbox: base image is fedora-toolbox:32
toolbox: container is fedora-toolbox-32
toolbox: checking value /run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: parsing value /run/.heim_org.h5l.kcm-socket (Stream) of property Listen in sssd-kcm.socket
toolbox: checking if 'podman create' supports --ulimit host
toolbox: 'podman create' supports --ulimit host
toolbox: looking for image localhost/fedora-toolbox:32
toolbox: looking for image registry.fedoraproject.org/f32/fedora-toolbox:32
Image required to create toolbox container.
Download registry.fedoraproject.org/f32/fedora-toolbox:32 (500MB)? [y/N]: y
toolbox: pulling image registry.fedoraproject.org/f32/fedora-toolbox:32
Trying to pull registry.fedoraproject.org/f32/fedora-toolbox:32...
Getting image source signatures
Copying blob 44e1bb1e1824 done  
Copying blob d589375e3582 done  
Copying config f7cf4b593f done  
Writing manifest to image destination
Storing signatures
toolbox: base image fedora-toolbox:32 resolved to registry.fedoraproject.org/f32/fedora-toolbox:32
toolbox: checking if container fedora-toolbox-32 already exists
toolbox: checking if /media is a symbolic link to /run/media
toolbox: checking if /mnt is a symbolic link to /var/mnt
toolbox: checking if /usr is mounted read-only or read-write
toolbox: mount-point of /usr is /
toolbox: mount flags of /usr on the host are rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota
toolbox: /home/bruno2 canonicalized to /home/bruno2
toolbox: checking if /home is a symbolic link to /var/home
toolbox: calling org.freedesktop.Flatpak.SessionHelper.RequestSession
toolbox: creating container fedora-toolbox-32
Created container: fedora-toolbox-32
Enter with: toolbox enter


toolbox -v list   
toolbox: running as real user ID 1002
toolbox: resolved absolute path for /usr/bin/toolbox to /usr/bin/toolbox
    toolbox: checking if /etc/subgid and /etc/subuid have entries for user bruno2
    toolbox: TOOLBOX_PATH is /usr/bin/toolbox
    toolbox: running on a cgroups v2 host
    toolbox: current Podman version is 1.8.2
    toolbox: migration not needed: Podman version 1.8.2 is unchanged
IMAGE ID      IMAGE NAME                                        CREATED
f7cf4b593fc1  registry.fedoraproject.org/f32/fedora-toolbox:32  4 weeks ago
CONTAINER ID  CONTAINER NAME     CREATED         STATUS   IMAGE NAME
4d467807ce76  fedora-toolbox-32  38 seconds ago  Created  registry.fedoraproject.org/f32/fedora-toolbox:32

Until then it went fine, but:

toolbox -v enter
toolbox: running as real user ID 1002
toolbox: resolved absolute path for /usr/bin/toolbox to /usr/bin/toolbox
toolbox: checking if /etc/subgid and /etc/subuid have entries for user bruno2
toolbox: TOOLBOX_PATH is /usr/bin/toolbox
toolbox: running on a cgroups v2 host
toolbox: current Podman version is 1.8.2
toolbox: migration not needed: Podman version 1.8.2 is unchanged
toolbox: Fedora generational core is f32
toolbox: base image is fedora-toolbox:32
toolbox: container is fedora-toolbox-32
toolbox: checking if container fedora-toolbox-32 exists
toolbox: calling org.freedesktop.Flatpak.SessionHelper.RequestSession
toolbox: starting container fedora-toolbox-32
toolbox: /etc/profile.d/toolbox.sh already mounted in container fedora-toolbox-32
toolbox: inspecting entry point of container fedora-toolbox-32
toolbox: entry point of container fedora-toolbox-32 is toolbox
toolbox: waiting for container fedora-toolbox-32 to finish initializing
toolbox: creating list of environment variables to forward
toolbox: COLORTERM=truecolor
toolbox: COLUMNS is unset
toolbox: DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus
toolbox: DBUS_SYSTEM_BUS_ADDRESS is unset
toolbox: DESKTOP_SESSION=gnome
toolbox: DISPLAY=:0
toolbox: LANG=en_US.UTF-8
toolbox: LINES is unset
toolbox: SHELL=/bin/zsh
toolbox: SSH_AUTH_SOCK=/run/user/1002/keyring/ssh
toolbox: TERM=xterm-256color
toolbox: TOOLBOX_PATH is unset
toolbox: VTE_VERSION=6001
toolbox: WAYLAND_DISPLAY=wayland-0
toolbox: XDG_CURRENT_DESKTOP=GNOME
toolbox: XDG_DATA_DIRS=/home/bruno2/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/
toolbox: XDG_MENU_PREFIX=gnome-
toolbox: XDG_RUNTIME_DIR=/run/user/1002
toolbox: XDG_SEAT is unset
toolbox: XDG_SESSION_DESKTOP=gnome
toolbox: XDG_SESSION_ID is unset
toolbox: XDG_SESSION_TYPE=wayland
toolbox: XDG_VTNR is unset
toolbox: created options for environment variables to forward
--env=COLORTERM=truecolor --env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus --env=DESKTOP_SESSION=gnome --env=DISPLAY=:0 --env=LANG=en_US.UTF-8 --env=SHELL=/bin/zsh --env=SSH_AUTH_SOCK=/run/user/1002/keyring/ssh --env=TERM=xterm-256color --env=VTE_VERSION=6001 --env=WAYLAND_DISPLAY=wayland-0 --env=XDG_CURRENT_DESKTOP=GNOME --env=XDG_DATA_DIRS=/home/bruno2/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/ --env=XDG_MENU_PREFIX=gnome- --env=XDG_RUNTIME_DIR=/run/user/1002 --env=XDG_SESSION_DESKTOP=gnome --env=XDG_SESSION_TYPE=wayland --env=COLUMNS=190 --env=LINES=54
toolbox: looking for /bin/zsh in container fedora-toolbox-32
Error: non zero exit code: 1: OCI runtime error
toolbox: /bin/zsh not found in fedora-toolbox-32; using /bin/bash instead
toolbox: running in container fedora-toolbox-32:
toolbox: /bin/bash
toolbox: -l
Error: chdir: No such file or directory: OCI runtime command not found error

Any idea what went wrong (note that I am not using Silverblue, just toolbox)

2

hello @brunovernay,
It may be this part here…

Perhaps the user environment variable passing with toolbox isn’t seeing zsh for some reason since this is where the OCI error seems to come from.
You could try to comment out the use of zsh and stick with bash if it works. I run zsh as my shell BTW, and I just created a container using your command string and was able to enter it no problem, but the shell is bash for sure.

1 Like
3

Strange: change nothing, wait a few days and …

 toolbox list
IMAGE ID      IMAGE NAME                                        CREATED
f7cf4b593fc1  registry.fedoraproject.org/f32/fedora-toolbox:32  5 weeks ago

CONTAINER ID  CONTAINER NAME     CREATED     STATUS                   IMAGE NAME
4d467807ce76  fedora-toolbox-32  3 days ago  Exited (143) 3 days ago  registry.fedoraproject.org/f32/fedora-toolbox:32
 ~ î‚° toolbox enter                     

Welcome to the Toolbox; a container where you can install and run
all your tools.

 - Use DNF in the usual manner to install command line tools.
 - To create a new tools container, run 'toolbox create'.

For more information, see the documentation.

bash: /usr/libexec/vte-urlencode-cwd: No such file or directory
⬢[bruno2@toolbox ~]$ 
bash: /usr/libexec/vte-urlencode-cwd: No such file or directory
⬢[bruno2@toolbox ~]$ dnf install java
Error: This command has to be run with superuser privileges (under the root user on most systems).
bash: /usr/libexec/vte-urlencode-cwd: No such file or directory
4

Had to follow bash: /usr/libexec/vte-urlencode-cwd: No such file or directory · Issue #390 · containers/toolbox · GitHub
I ran sudo dnf upgrade in toolbox and it fixed the thing.

Should be fixed soon 1815769 – please move /usr/libexec/vte-urlencode-cwd to vte-profile

Still can run dnf without sudo???

5

In toolbox ,yes you can since the user creates the container and becomes the root user for the container. Some commands will still require sudo, but you won’t need to enter a password for it in the container.

6

Actually, I cannot use dnf without sudo. I am the same user in the toolbox.
Also if I install zsh in the container, sudo dnf install zsh, it works, but I lose the ⬢ indicator sign in front of the prompt.

7

Yes that is correct you have to enter the command sudo but it is only because dnf expects a sudoer. The prompt will disappear from toolbox (from inside) once you changed the shell (to zsh) since it sources zprofile and zshrc in /etc (of your toolbox container) and .zprofile and .zshrc in your container user home. It is also important to note that your user environment and your system environment from the host system are shared with the container on entering it. Glad you got it working though.

1 Like
8

Actually the prompt was an issue with PowerLevel10k Context prompt is never shown if DEFAULT_USER is set · Issue #640 · romkatv/powerlevel10k · GitHub better not install fancy stuff if you want your system to work!

9

I use P10K on my Silverblue and it works fine for me.

10

After hours of debugging, it works fine for me too.
But you had to tweak it to enable the “toolbox diamond” to be displayed right?
Because the RPM installed /etc/profile.d/toolbox.sh only changes PS1. While p10k uses more fancy stuff.

11

The original bug looks like toolbox enter fails silently when pwd doesn't exist in container · Issue #369 · containers/toolbox · GitHub. It is a known bug and a new version of Toolbox should fix it (or at least handle it).

The line with not finding zsh and instead using bash is ok. Toolbox by default tries to use whatever is in SHELL env var but if it doesn’t find the tool in the container it fallbacks to bash.

Toolbox adds the current user to the container. It also adds the root user. Password of both the added user and root are deleted for convenience.

12

No the diamond prompt worked right away for me. P10K has no affect in my toolbox.