containers / containers/toolbox
Cannot enter container created from non-Toolbx image because /home is not empty
- Dominant language
- Go
- Stars
- 3.5k
- Forks
- 262
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Describe the bug**
I cannot enter a new container created with docker.io/rocker/r-bspm:latest when using toolbox on Fedora 41 Silverblue (Fedora Linux 41.20250408.0 (Silverblue)):
`toolbox create bspm --image docker.io/rocker/r-bspm:latest`
The following error is returned when attempting `toolbox enter bspm`:
Error: failed to redirect /home to /var/home: remove /home: directory not empty
DEBU Running as real user ID 1000
DEBU Resolved absolute path to the executable as /usr/bin/toolbox
DEBU Running on a cgroups v2 host
DEBU Looking up sub-GID and sub-UID ranges for user bryce
DEBU TOOLBX_DELAY_ENTRY_POINT is
DEBU TOOLBX_FAIL_ENTRY_POINT is
DEBU TOOLBOX_PATH is /usr/bin/toolbox
DEBU Migrating to newer Podman
DEBU Toolbx config directory is /var/home/bryce/.config/toolbox
DEBU Current Podman version is 5.4.1
DEBU Creating runtime directory /run/user/1000/toolbox
DEBU Old Podman version is 5.4.1
DEBU Migration not needed: Podman version 5.4.1 is unchanged
DEBU Setting up configuration
DEBU Setting up configuration: file /var/home/bryce/.config/containers/toolbox.conf not found
DEBU Resolving container and image names
DEBU Container: ''
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved container and image names
DEBU Container: 'fedora-toolbox-41'
DEBU Image: 'fedora-toolbox:41'
DEBU Release: '41'
DEBU Resolving container and image names
DEBU Container: 'bspm'
DEBU Distribution (CLI): ''
DEBU Image (CLI): ''
DEBU Release (CLI): ''
DEBU Resolved container and image names
DEBU Container: 'bspm'
DEBU Image: 'fedora-toolbox:41'
DEBU Release: '41'
DEBU Checking if container bspm exists
DEBU Inspecting container bspm
DEBU Entry point of container bspm is toolbox (PID=0)
DEBU Inspecting mounts of container bspm
DEBU Generating Container Device Interface for NVIDIA
DEBU Generating Container Device Interface for NVIDIA: Management Library not found: could not load NVML library: libnvidia-ml.so.1: cannot open shared object file: No such file or directory
DEBU Generating Container Device Interface for NVIDIA: not a Tegra system: /sys/devices/soc0/family file not found
DEBU Generating Container Device Interface for NVIDIA: skipping
DEBU Starting container bspm
DEBU Inspecting container bspm
DEBU Entry point of container bspm is toolbox (PID=0)
DEBU > Running as real user ID 0
DEBU > Resolved absolute path to the executable as /usr/bin/toolbox
DEBU > TOOLBX_DELAY_ENTRY_POINT is
DEBU > TOOLBX_FAIL_ENTRY_POINT is
DEBU > TOOLBOX_PATH is /usr/bin/toolbox
DEBU > Migrating to newer Podman
DEBU > Migration not needed: running inside a container
DEBU > Setting up configuration
DEBU > Setting up configuration: file /etc/containers/toolbox.conf not found
DEBU > Setting up configuration: file /root/.config/containers/toolbox.conf not found
DEBU > Resolving container and image names
DEBU > Container: ''
DEBU > Distribution (CLI): ''
DEBU > Image (CLI): ''
DEBU > Release (CLI): ''
DEBU > Resolved container and image names
DEBU > Container: 'fedora-toolbox-40'
DEBU > Image: 'fedora-toolbox:40'
DEBU > Release: '40'
DEBU > Creating /run/.toolboxenv
DEBU > Path /run/host/etc exists
DEBU > Resolved /etc/localtime to /run/host/usr/share/zoneinfo/America/Edmonton
DEBU > Creating regular file /etc/machine-id
DEBU > Binding /etc/machine-id to /run/host/etc/machine-id
DEBU > Creating directory /run/systemd/journal
DEBU > Binding /run/systemd/journal to /run/host/run/systemd/journal
DEBU > Creating directory /run/systemd/resolve
DEBU > Binding /run/systemd/resolve to /run/host/run/systemd/resolve
DEBU > Creating directory /run/systemd/sessions
DEBU > Binding /run/systemd/sessions to /run/host/run/systemd/sessions
DEBU > Creating directory /run/systemd/system
DEBU > Binding /run/systemd/system to /run/host/run/systemd/system
DEBU > Creating directory /run/systemd/users
DEBU > Binding /run/systemd/users to /run/host/run/systemd/users
DEBU > Creating directory /run/udev/data
DEBU > Binding /run/udev/data to /run/host/run/udev/data
DEBU > Creating directory /run/udev/tags
DEBU > Binding /run/udev/tags to /run/host/run/udev/tags
DEBU > Creating directory /tmp
DEBU > Binding /tmp to /run/host/tmp
DEBU > Creating directory /var/lib/flatpak
DEBU > Binding /var/lib/flatpak to /run/host/var/lib/flatpak
DEBU > Creating directory /var/lib/systemd/coredump
DEBU > Binding /var/lib/systemd/coredump to /run/host/var/lib/systemd/coredump
DEBU > Creating directory /var/log/journal
DEBU > Binding /var/log/journal to /run/host/var/log/journal
DEBU > Creating directory /var/mnt
DEBU > Binding /var/mnt to /run/host/var/mnt
DEBU > Preparing to redirect /home to /var/home
DEBU > /var/home isn't a symbolic link
Error: failed to redirect /home to /var/home: remove /home: directory not empty
**Expected behaviour**
I am able to enter the container.
**Actual behaviour**
The container cannot be entered and an error is printed to the console.
**Output of `toolbox --version` (v0.0.90+)**
toolbox version 0.1.1
**Toolbx package info (`rpm -q toolbox`)**
toolbox-0.1.1-1.fc41.x86_64
**Output of `podman version`**
```
Client: Podman Engine
Version: 5.4.1
API Version: 5.4.1
Go Version: go1.23.7
Git Commit: b79bc8afe796cba51dd906270a7e1056ccdfcf9e
Built: Mon Mar 10 18:00:00 2025
Build Origin: Fedora Project
OS/Arch: linux/amd64
```
**Podman package info (`rpm -q podman`)**
podman-5.4.1-1.fc41.x86_64
**Info about your OS**
Fedora Linux 41.20250408.0 (Silverblue)
**Additional context**
I saw this error the first time I attempted to enter the container after successfully creating it.
```
CONTAINER ID CONTAINER NAME CREATED STATUS IMAGE NAME
3d20320b1a1e bspm 7 minutes ago exited docker.io/rocker/r-bspm:testing
```
Contributor guide
Assessment
This issue has not been assessed yet.