WARN Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument Use "journald" if you want to change this setting and remove nf files.ĭEBU Reading configuration file "/usr/share/containers/nf"ĭEBU Merged system config "/usr/share/containers/nf": &ĭEBU Using conmon: "/usr/bin/conmon"ĭEBU Initializing boltdb state at /var/home/juanje/.local/share/containers/storage/libpod/bolt_state.dbĭEBU Using graph root /var/home/juanje/.local/share/containers/storageĭEBU Using run root /run/user/1000/containersĭEBU Using static dir /var/home/juanje/.local/share/containers/storage/libpodĭEBU Using tmp dir /run/user/1000/libpod/tmpĭEBU Using volume path /var/home/juanje/.local/share/containers/storage/volumesĭEBU trying provided driver "overlay"ĭEBU overlay: mount_program=/usr/bin/fuse-overlayfsĭEBU backingFs=extfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=falseĭEBU Initializing event backend file INFO podman filtering at log level debugĭEBU Called start.PersistentPreRunE(podman -log-level debug start fedora-toolbox-32)ĭEBU Ignoring nf EventsLogger setting "/var/home/juanje/.config/containers/nf". Here is the full error when I try to start the container with podman and set the log level to debug: $ podman -log-level debug start fedora-toolbox-32 I can create a new one and it’ll work, but my previous container won’t work, I’ve to remove it. The container exists and was working just fine before the reboot: $ toolbox listĭc930c1469f5 localhost/fedora-toolbox:32 3 weeks agoĬONTAINER ID CONTAINER NAME CREATED STATUS IMAGE NAMEħe628d2413b6 fedora-toolbox-32 1593148819 Created localhost/fedora-toolbox:32 Toolbox: /etc/profile.d/toolbox.sh already mounted in container fedora-toolbox-32Įrror: unable to start container "7e628d2413b6875d5ff30b64dc6121d4007280cce62bf79951bc0845ccacd873": setrlimit `RLIMIT_NPROC`: Operation not permitted: OCI runtime permission denied errorĪt this upgrade the package Podman changed to the 2.0 version, but at the previous upgrades the error was the same. Toolbox: starting container fedora-toolbox-32 Toolbox: checking if container fedora-toolbox-32 exists Toolbox: migration not needed: Podman version 2.0.2 is unchanged Toolbox: checking if /etc/subgid and /etc/subuid have entries for user juanje Toolbox: failed to start container fedora-toolbox-32 Each time I do an rpm-ostree upgrade and then I reboot, I get the same error: $ toolbox enter Toolbox: failed to create /run/.toolboxenv in container fedora-toolbox-31 Toolbox: waiting for container fedora-toolbox-31 to finish initializingĮrror: unable to find user root: no matching entries in passwd file Toolbox: entry point of container fedora-toolbox-31 is toolbox Toolbox: inspecting entry point of container fedora-toolbox-31 Toolbox: /etc/profile.d/toolbox.sh already mounted in container fedora-toolbox-31 Toolbox: starting container fedora-toolbox-31 Toolbox: checking if container fedora-toolbox-31 exists Toolbox: migration not needed: Podman version 1.6.2 is unchanged Toolbox: TOOLBOX_PATH is /usr/bin/toolbox Toolbox: checking if /etc/subgid and /etc/subuid have entries for user mike Toolbox: resolved absolute path for /usr/bin/toolbox to /usr/bin/toolbox Toolbox: failed to create /run/.toolboxenv in container ~]$ toolbox -v enter Here is what I get when I try to toolbox -v enter: ~]$ toolbox enter I am still getting same error with 31.20191207.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |