Invalid entry point for specific (working) image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
golang-github-containers-toolbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
$ lsb_release -rd
Description: Ubuntu 22.04.1 LTS
Release: 22.04
$ apt-cache policy podman-toolbox
podman-toolbox:
Installed: 0.0.99.2-2ubuntu1
Candidate: 0.0.99.2-2ubuntu1
Version table:
*** 0.0.99.2-2ubuntu1 500
500 http://
100 /var/lib/
I tried to use an Ubuntu 20.04 image with toolbox (image from here https:/
I am able to create the toolbox without any problems, but I am unable to enter it (Error: invalid entry point PID of container ubuntu-
$ toolbox create --image quay.io/
Image required to create toolbox container.
Download quay.io/
Created container: ubuntu-
Enter with: toolbox enter ubuntu-
$ toolbox --verbose enter ubuntu-
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 Checking if /etc/subgid and /etc/subuid have entries for user niklas
DEBU Validating sub-ID file /etc/subuid
DEBU Validating sub-ID file /etc/subgid
DEBU TOOLBOX_PATH is /usr/bin/toolbox
DEBU Migrating to newer Podman
DEBU Toolbox config directory is /home/niklas/
DEBU Current Podman version is 3.4.4
DEBU Creating runtime directory /run/user/
DEBU Old Podman version is 3.4.4
DEBU Migration not needed: Podman version 3.4.4 is unchanged
DEBU Resolving container and image names
DEBU Container: 'ubuntu-
DEBU Distribution: ''
DEBU Image: ''
DEBU Release: ''
DEBU Resolved container and image names
DEBU Container: 'ubuntu-
DEBU Image: 'fedora-toolbox:33'
DEBU Release: '33'
DEBU Checking if container ubuntu-
DEBU Inspecting mounts of container ubuntu-
DEBU Starting container ubuntu-
DEBU Inspecting entry point of container ubuntu-
DEBU Entry point PID is a float64
DEBU Entry point of container ubuntu-
Error: invalid entry point PID of container ubuntu-
I created an issue on github in the repository of the Ubuntu images https:/
Would it be possible to update toolbox to 0.0.99.3 (which was released last December).
BTW, I think an similar error occurs when running the default image (somehow set to fedora-toolbox-33).