Package: podman-toolbox Version: 0.0.99.3-1 Severity: important X-Debbugs-Cc: david.hal...@fau.de
Creating a toolbox container with "toolbox create" and running it with "toolbox enter" works as expected. It uses the image fedora-toolbox:34 per default. As I wanted to use a more recent version of Fedora, I changed my command to "toolbox create -r 36" which runs successfully, but toolbox -v enter fedora- toolbox-36 give the error message "Error: invalid entry point PID of container fedora-toolbox-36" I also tried an image with RHEL and one with Arch Linux, both give the same error message. When I add the -v option to my toolbox command, something interesting happens: DEBU Container: 'arch' DEBU Image: 'fedora-toolbox:34' DEBU Release: '34' It seems to me, that toolbox always uses the image for Fedora 34, even if you explicitly tell them to use a different image, like Fedora 36, RHEL 9, Arch Linux, or Debian. toolbox create -c debian -i docker.io/library/debian:latest toolbox enter debian DEBU Container: 'debian' DEBU Image: 'fedora-toolbox:34' DEBU Release: '34' Maybe I am just stupid, or the image name is hardcoded to "fedora-toolbox:34". When I delete all my downloaded images and containers, the behavior stays the same. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages podman-toolbox depends on: ii flatpak 1.12.7-1 ii libc6 2.33-7 ii podman 3.4.7+ds1-3+b1 ii uidmap 1:4.11.1+dfsg1-2 Versions of packages podman-toolbox recommends: ii bash-completion 1:2.11-6 podman-toolbox suggests no packages. -- no debconf information
