-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman: panic: runtime error: invalid memory address or nil pointer dereference #20250
Comments
Including podman version/info
|
©petrkr Not sure, but didn't 3.4.1 fix this issue? Or some of the newer ones? My webserver (yes, my site's server runs on openwrt) - has been running with podman 3.4.4 ever since I updated to that version. There's weekly reboots on server, but it has nothing to do with podman.... Should update the whole system. Btw. why is mine using cgroupv1 when you clearly have cgroupv2..? Otherwise your setup seems just like mine that runs without issues except that is a bit older, and:
One thing though pops... You are using runc as oci runtime. Would you mind trying first with crun, as it's recommended for podman over runc. I have never updated anything but master versions, current is running with 4.3.0 and I should be today, updating the build to 4.3.1. My main router is running with 4.3.0 as far as I know- without bigger problem, with basic alpine:latest and tmux keeps it up.. EDIT: |
But try switch to crun first. |
I did not mentioned it, but I've triee both, runc and crun, same results |
Ok, so you need a updated version then. I can verify that 3.4.4 works fine. |
Can not update as package is not compiled. That is what I wrote on original issue.. if someone have working build environment, maybe can put and build 3.4.4 and I can test. But in 21.02 repo is still 3.4.1 |
I have, but wrong arch- mine is x86-64.. There's though even newer version available, though I am not sure if other system depencies are filled- Snapshots: podman_4.3.1-1 Double check the download path, there were alternatives for arm cortex a9 and I know nothing about turris. |
yes, there will be dependency hell as this package will be probably from 22/master branch. |
That is possible. I pushed it few weeks ago to master. |
Updating to 3.4.7 helps, but I am still having issues:
and this on any subsequent runs:
I didn't manage to build 4.3.1 on OpenWrt 21.02 even though gpg-error.pc is in
|
Can you please share that ipkg/opkg ? I will try to check this other stuff... But I hope it's not kernel config related |
podman_3.4.7-1_arm_cortex-a9_vfpv3-d16.zip GitHub didn't allow me to upload an .ipk file, so just change the extension from zip to ipk. |
Well. this is at-least interesting error message in syslog
but what kind of kernel module or folder it looking for ? EDIT:
|
well, kernel module was just because OpenWRT updated to new kernel without reboot. So ignore that message. |
Just wonder if new version of "conmon" can fix it
in OpenWRT 21.02 is 2.0.30 |
Latest conmon is 2.1.5 - available at snapshots. |
Again, seems I can not use snapshot version in 21.02 OpenWRT
|
conmon 2.1.5 and libseccomp 2.5.2 which was required for the build for OpenWrt 21.02: I am still getting the |
There could be missing something in kernel. I check that debug message and it can not get terminal info, but which terminal? Container's or system (turris one). I also tried all three runc, crun, uxc... actually uxc ends with "I/O Error" but since they missing lot of debug prints, I really do not know which part of 2000 lines C file ends with return -1 |
remember to put uxc to different group, if I remember correctly, it doesn't support json like those 2 others- but nevertheless, uxc won't work anyway, I tested that sometime ago as well.. |
Maintainer: Oskari Rauta
Environment: ARMv7 - Turris Omnia - OpenWRT 21.02 (Turris OS 6.2.1)
Description:
Seems same problem like this one containers/podman#10535
Just wonder if update to latest 3.4.x podman version (https://github.com/containers/podman/releases?q=v3.4&expanded=true) would fix that. It is hard for me to set-up whole build environment to rebuild just one package to test it
Package makefile: https://git.openwrt.org/?p=feed/packages.git;a=blob;f=utils/podman/Makefile;h=e8323d4022e0b332a00a0ef4c7ba17e3fae0debf;hb=refs/heads/openwrt-21.02
i've tried overlay and btrfs (as there is Btrfs filesystem) storage engine, both are same.
The text was updated successfully, but these errors were encountered: