Skip to content
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

Closed
Elrondo46 opened this issue May 25, 2023 · 13 comments
Closed

Crun permission denied in podman since kernel 6.1.28 #5483

Elrondo46 opened this issue May 25, 2023 · 13 comments

Comments

@Elrondo46
Copy link

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

@Elrondo46 Elrondo46 changed the title Crun permission denied in podman since kernel 4.1.28 Crun permission denied in podman since kernel 6.1.28 May 26, 2023
@Elrondo46
Copy link
Author

sorry for bad kernel number in title

@pelwell
Copy link
Contributor

pelwell commented May 26, 2023

Is it a 32-bit or 64-bit Arch? If 32-bit, does adding arm_64bit=0 to config.txt make a difference?

@Elrondo46
Copy link
Author

Elrondo46 commented May 26, 2023 via email

@pelwell
Copy link
Contributor

pelwell commented May 26, 2023

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.

@Elrondo46
Copy link
Author

Elrondo46 commented May 26, 2023 via email

@pelwell
Copy link
Contributor

pelwell commented May 26, 2023

What was the last working version? You don't make it clear whether 6.1.27 works or doesn't.

@Elrondo46
Copy link
Author

In 6.1.27, podman in rootless working without problems. Downgrading successfully. It's since 6.1.28 the problem appears.

@pelwell
Copy link
Contributor

pelwell commented May 26, 2023

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

@Elrondo46
Copy link
Author

Elrondo46 commented May 26, 2023

Submitted, I post if I have a solution from them of if they redirect to you

containers/podman#18696

@pelwell
Copy link
Contributor

pelwell commented May 26, 2023

Thanks - I hope that have some suggestions.

@Elrondo46
Copy link
Author

They redirect the bug solving to a kernel cause

containers/podman#18696 (comment)

@Elrondo46
Copy link
Author

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...

@pelwell
Copy link
Contributor

pelwell commented May 26, 2023

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.

@pelwell pelwell closed this as completed May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants