Repository navigation
Commit 956ccb5
committed
fix(supervisor): tolerate non-empty bounding set when CAP_SETPCAP is unavailable
On rootless Podman with AppArmor unprivileged user namespace restrictions
(Ubuntu 24.04 default), CAP_SETPCAP is granted by Podman but blocked at
the kernel level by AppArmor. This causes drop_capability_bounding_set()
to fail with EPERM while the bounding set is non-empty — a case that was
unhandled, crashing sandbox creation.
Add a match arm that logs a warning and continues when EPERM is returned
with a non-empty bounding set. The child process is still confined by
seccomp and Landlock.
Fixes: NVIDIA#2069
Assisted-by: Claude
Signed-off-by: Wayne Sun <[email protected]>1 parent 5477e2f commit 956ccb5
1 file changed
Lines changed: 16 additions & 13 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
26 | 26 | | |
27 | 27 | | |
28 | 28 | | |
29 | | - | |
| 29 | + | |
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
| |||
189 | 189 | | |
190 | 190 | | |
191 | 191 | | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
192 | 200 | | |
193 | 201 | | |
194 | 202 | | |
| |||
1150 | 1158 | | |
1151 | 1159 | | |
1152 | 1160 | | |
1153 | | - | |
| 1161 | + | |
1154 | 1162 | | |
1155 | 1163 | | |
1156 | 1164 | | |
1157 | | - | |
1158 | | - | |
1159 | | - | |
1160 | | - | |
1161 | | - | |
1162 | | - | |
1163 | | - | |
1164 | 1165 | | |
1165 | | - | |
1166 | | - | |
1167 | | - | |
1168 | | - | |
| 1166 | + | |
| 1167 | + | |
| 1168 | + | |
| 1169 | + | |
| 1170 | + | |
| 1171 | + | |
1169 | 1172 | | |
1170 | 1173 | | |
1171 | 1174 | | |
| |||
0 commit comments