No idea what caused this, but suddenly toolbox enter fails starting container
e.g
DEBU Inspecting container fedora-toolbox-43
DEBU Entry point of container fedora-toolbox-43 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-43'
DEBU > Image: 'fedora-toolbox:43'
DEBU > Release: '43'
DEBU > Creating /run/.toolboxenv
DEBU > Path /run/host/etc exists
DEBU > Resolved /etc/localtime to /run/host/usr/share/zoneinfo/Europe/Berlin
DEBU > Creating regular file /etc/machine-id
DEBU > Binding /etc/machine-id to /run/host/etc/machine-id
Error: mount: /etc/machine-id: must be superuser to use mount.
dmesg(1) may have more information after failed mount system call.
failed to bind /etc/machine-id to /run/host/etc/machine-id
dmesg shows nothing,
However I can start containers for new downloaded images
I purged the fedora 44 image and then toolbox create + toolbox enter worked as expected.
DEBU Inspecting container fedora-toolbox-44
DEBU Entry point of container fedora-toolbox-44 is toolbox (PID=139733)
DEBU Waiting for container fedora-toolbox-44 to finish initializing
DEBU Checking if initialization stamp /run/user/1000/toolbox/container-initialized-139733 exists
DEBU Setting up initialization timeout for container fedora-toolbox-44
DEBU Following logs for container fedora-toolbox-44
DEBU Setting up watches for file system events from container fedora-toolbox-44
DEBU Listening to container, ticker and timeout events
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-44'
DEBU > Image: 'fedora-toolbox:44'
DEBU > Release: '44'
DEBU > Creating /run/.toolboxenv
DEBU > Path /run/host/etc exists
DEBU > Resolved /etc/localtime to /run/host/usr/share/zoneinfo/Europe/Berlin
DEBU > Creating regular file /etc/machine-id
DEBU > Binding /etc/machine-id to /run/host/etc/machine-id
DEBU > Creating directory /run/libvirt
DEBU > Binding /run/libvirt to /run/host/run/libvirt
DEBU > Creating directory /run/systemd/journal
DEBU > Binding /run/systemd/journal to /run/host/run/systemd/journal
DEBU > Creating directory /run/systemd/resolve
any ideas what caused this and how to fix?
the only difference seems to be
fail:
DEBU Entry point of container fedora-toolbox-43 is toolbox (PID=0)
OK:
DEBU Entry point of container fedora-toolbox-44 is toolbox (PID=139733)
DEBU Waiting for container fedora-toolbox-44 to finish initializing
DEBU Checking if initialization stamp /run/user/1000/toolbox/container-initialized-139733 exists
DEBU Setting up initialization timeout for container fedora-toolbox-44
DEBU Following logs for container fedora-toolbox-44
DEBU Setting up watches for file system events from container fedora-toolbox-44
DEBU Listening to container, ticker and timeout events