toolbox: Container doesn't start because of missing /media possibly due to failed RPM transaction

[bam@host ~]$ toolbox --verbose  enter --container kde.f33
DEBU Running as real user ID 1001                 
DEBU Resolved absolute path to the executable as /usr/bin/toolbox 
DEBU Running on a cgroups v2 host                 
DEBU Checking if /etc/subgid and /etc/subuid have entries for user bam 
DEBU TOOLBOX_PATH is /usr/bin/toolbox             
DEBU Toolbox config directory is /home/bam/.config/toolbox 
DEBU Current Podman version is 2.0.4              
DEBU Old Podman version is 2.0.4                  
DEBU Migration not needed: Podman version 2.0.4 is unchanged 
DEBU Resolving container and image names          
DEBU Container: 'kde.f33'                         
DEBU Image: ''                                    
DEBU Release: ''                                  
DEBU Resolved container and image names           
DEBU Container: 'kde.f33'                         
DEBU Image: 'fedora-toolbox:32'                   
DEBU Release: '32'                                
DEBU Checking if container kde.f33 exists         
DEBU Calling org.freedesktop.Flatpak.SessionHelper.RequestSession 
DEBU Starting container kde.f33                   
DEBU Inspecting entry point of container kde.f33  
DEBU Entry point PID is a float64                 
DEBU Entry point of container kde.f33 is toolbox (PID=0) 
Error: invalid entry point PID of container kde.f33

[bam@host ~]$ toolbox --version
toolbox version 0.0.93

[bam@host ~]$ podman start --attach kde.f33
level=debug msg="Running as real user ID 0"
level=debug msg="Resolved absolute path to the executable as /usr/bin/toolbox"
level=debug msg="TOOLBOX_PATH is /usr/bin/toolbox"
level=debug msg="XDG_RUNTIME_DIR is unset"
level=debug msg="XDG_RUNTIME_DIR set to /run/user/1001"
level=debug msg="Creating /run/.toolboxenv"
level=debug msg="Monitoring host"
level=debug msg="Path /run/host/etc exists"
level=debug msg="Binding /etc/machine-id to /run/host/etc/machine-id"
level=debug msg="Creating /run/systemd/journal"
level=debug msg="Binding /run/systemd/journal to /run/host/run/systemd/journal"
level=debug msg="Creating /var/lib/flatpak"
level=debug msg="Binding /var/lib/flatpak to /run/host/var/lib/flatpak"
level=debug msg="Creating /var/log/journal"
level=debug msg="Binding /var/log/journal to /run/host/var/log/journal"
level=debug msg="Creating /var/mnt"
level=debug msg="Binding /var/mnt to /run/host/var/mnt"
level=debug msg="Creating /sys/fs/selinux"
level=debug msg="Binding /sys/fs/selinux to /usr/share/empty"
level=debug msg="Path /run/host/monitor exists"
level=debug msg="Redirecting /media to /run/media"
Error: failed to redirect /media to /run/media

I don’t see that /media line at all when attaching to f32 container:

[bam@host ~]$ podman --log-level debug start --attach kde.f32
....                    
level=debug msg="Running as real user ID 0"
level=debug msg="Resolved absolute path to the executable as /usr/bin/toolbox"
level=debug msg="TOOLBOX_PATH is /usr/bin/toolbox"
level=debug msg="XDG_RUNTIME_DIR is unset"
level=debug msg="XDG_RUNTIME_DIR set to /run/user/1001"
level=debug msg="Creating /run/.toolboxenv"
level=debug msg="Monitoring host"
level=debug msg="Path /run/host/etc exists"
level=debug msg="Binding /etc/machine-id to /run/host/etc/machine-id"
level=debug msg="Creating /run/systemd/journal"
level=debug msg="Binding /run/systemd/journal to /run/host/run/systemd/journal"
level=debug msg="Creating /var/lib/flatpak"
level=debug msg="Binding /var/lib/flatpak to /run/host/var/lib/flatpak"
level=debug msg="Creating /var/log/journal"
level=debug msg="Binding /var/log/journal to /run/host/var/log/journal"
level=debug msg="Creating /var/mnt"
level=debug msg="Binding /var/mnt to /run/host/var/mnt"
level=debug msg="Creating /sys/fs/selinux"
level=debug msg="Binding /sys/fs/selinux to /usr/share/empty"
level=debug msg="Path /run/host/monitor exists"
level=debug msg="Finished initializing container"
level=debug msg="Creating runtime directory /run/user/1001/toolbox"
level=debug msg="Creating initialization stamp /run/user/1001/toolbox/container-initialized-17636"
level=debug msg="Going to sleep"
DEBU[0137] Sending signal 28 to container 3cda239851f1cb2706cc312490e6b75b568eb1e1f92c56f52bd1ea924674d547

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 19 (11 by maintainers)

Commits related to this issue

cmd/initContainer: Do create a symlink if the containerPath was absent The redirectPath function used to error out when handling directories, if the path inside the container was initially absent. Th... — committed to HarryMichal/toolbox by HarryMichal 4 years ago
cmd/initContainer: Do create a symlink if the containerPath was absent The redirectPath function used to error out when handling directories, if the path inside the container was initially absent. Th... — committed to HarryMichal/toolbox by HarryMichal 4 years ago
cmd/initContainer: Do create a symlink if the containerPath was absent The redirectPath function used to error out when handling directories, if the path inside the container was initially absent. Th... — committed to likan999/ppa-toolbox by HarryMichal 4 years ago

Most upvoted comments

Confirmed - did something like:

$ toolbox create -c f33-to-upgrade -i f33/fedora-toolbox:f33-4
$ toolbox enter f33-to-upgrade
$ dnf -y --enablerepo=fedora --disablerepo=rawhide update
<...>
Failed:
  filesystem-3.14-2.fc32.x86_64                                                         filesystem-3.14-3.fc33.x86_64                                                        

Error: Transaction failed
$ ls -l /media
ls: cannot access '/media': No such file or directory

owtaylor on Oct 1, 2020

Workaround I used:

$ podman unshare /bin/bash
# cd $(podman mount fedora-toolbox-33)
# ln -s /run/media .
# exit

owtaylor on Sep 9, 2020

I doubt how I can try Toolbox 0.0.94 on Fedora Silverblue 32.

I created an update for Fedora 32 just now. You can use rpm-ostree to override the toolbox package that’s in your OS image.

Can I run Toolbox from within Toolbox? 😃

Yes, but it will still be the version that’s on your host.

debarshiray on Aug 26, 2020