-
Notifications
You must be signed in to change notification settings - Fork 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
Crun permission denied in podman since kernel 6.1.28 #5483
Comments
sorry for bad kernel number in title |
Is it a 32-bit or 64-bit Arch? If 32-bit, does adding |
It's 64bit arch
26 mai 2023 10:39:28 Phil Elwell ***@***.***>:
…
Is it a 32-bit or 64-bit Arch? If 32-bit, does adding *arm_64bit=0* to config.txt make a difference?
—
Reply to this email directly, view it on GitHub[#5483 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AEKOBHNXF7ATDU7CZLRPOBDXIBT33ANCNFSM6AAAAAAYPHIPGU].
You are receiving this because you authored the thread.[Image de pistage][https://github.com/notifications/beacon/AEKOBHJPUKAWSDAYQWS45YDXIBT33A5CNFSM6AAAAAAYPHIPGWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS5HEIYO.gif]
|
In that case I don't think you'll get much help here, unless you can identify what is causing the problem. You might have more luck asking the Podman devs. |
Hi,
But this is after the kernel 6.1.27, there is a problem. Not before it…
De : Phil ***@***.***>
Envoyé le :vendredi 26 mai 2023 11:13
À : ***@***.***>
Cc : ***@***.***>; ***@***.***>
Objet :Re: [raspberrypi/linux] Crun permission denied in podman since kernel 6.1.28 (Issue #5483)
In that case I don't think you'll get much help here, unless you can identify what is causing the problem. You might have more luck asking the Podman devs.
—
Reply to this email directly, view it on GitHub<#5483 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEKOBHLMNTWMR5CYNA47UPDXIBX4LANCNFSM6AAAAAAYPHIPGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
What was the last working version? You don't make it clear whether 6.1.27 works or doesn't. |
In 6.1.27, podman in rootless working without problems. Downgrading successfully. It's since 6.1.28 the problem appears. |
The podman devs are still much more likely to know what is going wrong (especially when you've provided so little information): https://github.com/containers/podman/issues |
Submitted, I post if I have a solution from them of if they redirect to you |
Thanks - I hope that have some suggestions. |
They redirect the bug solving to a kernel cause |
Please note, users have to recreate pods to be compatible with the last kernel 6.1.28 or 6.1.29. Thats the first time I had this problem... |
So some upstream kernel change (not one of ours) has caused a parameter saved at "pod" creation to no longer be valid. The Podman team may find a way to handle that more gracefully, but for now you have a workaround. |
Describe the bug
Use rlimit in podman engine at rootless results as permission denied. Tested in two rpi4 in Arch Arm
Steps to reproduce the behaviour
Upgrade to last kernels and you can't start any pods
Device (s)
Raspberry Pi 4 Mod. B
System
Kernel 6.1.27 or 6.1.28 all subversions in Arch ARM
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: