Replies: 3 comments 1 reply
-
No schedule, hope we can release it by the end of the year...
Yes. If you find some incompatibility, please notify us.
Probably too big to cherry-pick, but I think this one is negotiable. |
Beta Was this translation helpful? Give feedback.
-
|
It should be noted that the code in the PR you linked was quite significantly reworked in #3967 (also slated to be in 1.2.0). It really depends on what you mean by "backwards compatible". There are certain cases where runc had broken behaviour and those have been fixed, so if you depended on the broken behaviour (i.e. behaviour where many flags were ignored when configuring bind-mounts) then you would have issues. But it seems very unlikely anyone depended on the broken behaviour, because it means you were setting an option you didn't want and didn't care that it was ignored. Sane configurations will work the same as before though. As for backporting, the changes are a bit too complicated to backport and we do not intend to maintain the 1.1.z branch after the 1.2.0 release, so backporting it when we plan to release 1.2.0 makes little sense IMHO. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I will test new snapshot of |
Beta Was this translation helpful? Give feedback.
-
|
OK, thank you very much for your answers. I think the best way for me is to wait for the 1.2.0 release and don't create additional work. :-) |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm a bit interested into the Allow bind mounts of nodev,nosuid,noexec filesystems. This issue blocks KinD and K3D in rootless Podman.
I've seen the issue is scheduled for the 1.2.0 milestone. I have a few questions in this regard:
Thank you very much for your time.
PETR
Beta Was this translation helpful? Give feedback.
All reactions