containers / containers/toolbox
cannot podman pull image inside toolbox
- Dominant language
- Go
- Stars
- 3.5k
- Forks
- 262
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Describe the bug**
(Well this may be expected/known, but I thought I would ask here anyway.)
It does not seem possible to `podman pull` images from inside a toolbox.
**Steps how to reproduce the behaviour**
`$ podman pull quay.io/centos/centos:stream10`
**Expected behaviour**
Container image to be pulled
**Actual behaviour**
```
ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": cannot re-exec process to join the existing user namespace
```
**Output of `toolbox --version` (v0.0.90+)**
0.1.1
**Toolbx package info (`rpm -q toolbox`)**
toolbox-0.1.1-3.fc42.x86_64
**Output of `podman version`**
```
Client: Podman Engine
Version: 5.5.0
API Version: 5.5.0
Go Version: go1.24.3
Git Commit: 0dbcb51477ee7ab8d3b47d30facf71fc38bb0c98
Built: Wed May 14 02:00:00 2025
Build Origin: Fedora Project
OS/Arch: linux/amd64
```
**Podman package info (`rpm -q podman`)**
podman-5.5.0-1.fc42.x86_64
**Info about your OS**
Fedora Silverblue 42 (maybe bump "32" in the template ;o)
Contributor guide
Research direction
Start by reproducing the reported `podman pull quay.io/centos/centos:stream10` failure inside toolbox on Fedora Silverblue 42, using the listed toolbox and Podman versions. Trace the interaction that produces the user-namespace re-exec error and compare it with running the same command outside toolbox. Done means image pulls successfully inside toolbox or the limitation is documented with a clear explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fedora, go, linux
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100