On Fedora this is shipped here /usr/libexec/podman/rootlessport $ rpm -qf /usr/libexec/podman/rootlessport podman-4.1.1-1.fc36.x86_64 It is shipped inside of the podman package. If you are building from source, you should be able to do make bin/rootlessport On 7/14/22 15:56, Loren Amelang wrote:
I have no idea what this means, but you're not alone missing "rootlessport":
pi@raspberrypi:~/tripod $ podman version Version: 3.0.1 API Version: 3.0.0 Go Version: go1.15.15 Built: Wed Dec 31 16:00:00 1969 OS/Arch: linux/arm pi@raspberrypi:~/tripod $
pi@raspberrypi:~/tripod $ sudo find / -name "*rootlessport*" pi@raspberrypi:~/tripod $
pi@raspberrypi:~/tripod $ ls -al /usr/local/libexec/ ls: cannot access '/usr/local/libexec/': No such file or directory pi@raspberrypi:~/tripod $ ls -al /usr/local/lib/ total 20 drwxr-xr-x 5 root root 4096 May 20 01:17 . drwxr-xr-x 10 root root 4096 Jan 25 14:12 .. drwxr-xr-x 3 root root 4096 Jan 25 14:12 node_modules drwxr-xr-x 3 root root 4096 Oct 30 2021 python3.9 drwxr-xr-x 3 root root 4096 May 20 01:17 R pi@raspberrypi:~/tripod $ ls -al /usr/libexec/ total 1028 drwxr-xr-x 5 root root 4096 Jun 6 13:27 . drwxr-xr-x 11 root root 4096 Oct 30 2021 .. -rwxr-xr-x 1 root root 74460 Apr 22 2021 at-spi2-registryd -rwxr-xr-x 1 root root 18016 Apr 22 2021 at-spi-bus-launcher drwxr-xr-x 2 root root 4096 Oct 30 2021 bluetooth -rwxr-xr-x 1 root root 329376 Nov 11 2020 colord -rwxr-xr-x 1 root root 9816 Nov 11 2020 colord-sane -rwxr-xr-x 1 root root 42584 Nov 11 2020 colord-session drwxr-xr-x 2 root root 4096 Oct 30 2021 coreutils -rwxr-xr-x 1 root root 71136 Feb 4 2021 dconf-service -rwxr-xr-x 1 root root 13780 Sep 27 2020 glib-pacrunner -rwxr-xr-x 1 root root 232712 Dec 22 2020 packagekitd -rwxr-xr-x 1 root root 80188 Dec 22 2020 packagekit-direct -rwxr-xr-x 1 root root 5800 Dec 22 2020 pk-debconf-helper -rwxr-xr-x 1 root root 18308 Dec 22 2020 pk-offline-update drwxr-xr-x 2 root root 4096 Jun 6 13:27 podman -rwsr-xr-x 1 root root 14128 Jun 22 2021 polkit-agent-helper-1 -rwxr-xr-x 1 root root 92996 Jun 22 2021 polkitd pi@raspberrypi:~/tripod $ ls -al /usr/libexec/podman total 8 drwxr-xr-x 2 root root 4096 Jun 6 13:27 . drwxr-xr-x 5 root root 4096 Jun 6 13:27 .. lrwxrwxrwx 1 root root 19 Dec 9 2020 catatonit -> ../../bin/catatonit pi@raspberrypi:~/tripod $ ls -al /usr/lib/podman ls: cannot access '/usr/lib/podman': No such file or directory pi@raspberrypi:~/tripod $ ls -al /usr/lib/ total 3260 [tons of other packages... No podman]
But I don't get your error:
pi@raspberrypi:~/tripod $ podman --log-level=debug run -p 6379:6379 -d docker.io/library/redis:7.0 INFO[0000] podman filtering at log level debug DEBU[0000] Called run.PersistentPreRunE(podman --log-level=debug run -p 6379:6379 -d docker.io/library/redis:7.0) DEBU[0000] Reading configuration file "/usr/share/containers/containers.conf"
...
INFO[0000] Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument
[That's the problem I'm struggling with - anything I try to run dies in a second.]
...
[But my rootlessport claims success:]
DEBU[0002] rootlessport: time="2022-07-14T12:17:11-07:00" level=info msg="starting parent driver" DEBU[0002] rootlessport: time="2022-07-14T12:17:11-07:00" level=info msg="opaque=map[builtin.readypipepath:/run/user/1000/libpod/tmp/rootlessport636652339/.bp-ready.pipe builtin.socketpath:/run/user/1000/libpod/tmp/rootlessport636652339/.bp.sock]"
DEBU[0002] rootlessport: time="2022-07-14T12:17:11-07:00" level=info msg="starting child driver in child netns (\"/proc/self/exe\" [containers-rootlessport-child])" DEBU[0002] rootlessport: time="2022-07-14T12:17:11-07:00" level=info msg="waiting for initComplete" DEBU[0003] rootlessport: time="2022-07-14T12:17:12-07:00" level=info msg="initComplete is closed; parent and child established the communication channel" DEBU[0003] rootlessport: time="2022-07-14T12:17:12-07:00" level=info msg="exposing ports [{6379 6379 tcp }]" DEBU[0003] rootlessport: time="2022-07-14T12:17:12-07:00" level=info msg=ready DEBU[0003] rootlessport is ready
...
DEBU[0003] Called run.PersistentPostRunE(podman --log-level=debug run -p 6379:6379 -d docker.io/library/redis:7.0) pi@raspberrypi:~/tripod $
The container exited in about a second:
pi@raspberrypi:~/tripod $ podman ps -a 84714b0d8b04 docker.io/library/redis:7.0 redis-server About a minute ago Exited (139) About a minute ago 0.0.0.0:6379->6379/tcp suspicious_khorana pi@raspberrypi:~/tripod $
No persistent port 6379 open.
Not sure what else to say, but I learn from exploring such things! Would be great if someone could explain these error reports...
Loren
On 7/13/2022 7:29 PM, None via Podman wrote:
When I run "podman run -p 6379:6379 -d redis:7.0", the error as following.
Error: could not find "rootlessport" in one of [/usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman]. To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries.
Any help will be appreciated.
----------------------------------- $ podman version Client: Podman Engine Version: 4.0.2 API Version: 4.0.2 Go Version: go1.16.13 Git Commit: c99f9f1b6960b98158b7f5fc4e6b5ac1a10b3542 Built: Wed Mar 23 18:33:41 2022 OS/Arch: linux/amd64 _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io