-
Notifications
You must be signed in to change notification settings - Fork 68
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
Create xtables.lock as a file if it doesn't already exist #2822
Conversation
Default host path mounts create a directory if the mounted path doesn't correspond to anything, which ends up breaking iptables. This fixes that by ensuring that xtables.lock is created as a file if it doesn't already exist; subsequent invocations of iptables on the host (if any) will then be able to use the new file for locking. Signed-off-by: Stephen Kitt <skitt@redhat.com>
🤖 Created branch: z_pr2822/skitt/qualify-xtables-host-path |
This seems to cause a vulnerability error. |
The vulnerability is a false positive, see github/advisory-database#2742 |
OK. I changed the job to required - did you make it non-required due to this? |
Yes — we can wait for the advisory fix to be merged, or “unrequire” the job until it’s fixed... |
🤖 Closed branches: [z_pr2822/skitt/qualify-xtables-host-path] |
…2822-origin-release-0.14
Default host path mounts create a directory if the mounted path doesn't correspond to anything, which ends up breaking iptables. This fixes that by ensuring that xtables.lock is created as a file if it doesn't already exist; subsequent invocations of iptables on the host (if any) will then be able to use the new file for locking.