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

clean up CNI results cache on boot #3792

Merged
merged 1 commit into from
Feb 22, 2024

Conversation

bcressey
Copy link
Contributor

Issue number:

Related: containerd/containerd#8197

Description of changes:
The network device configurations referenced in the results do not persist across reboot, so the cache isn't useful. Malformed or empty files can also cause errors that interfere with subsequent operations on pod sandboxes.

Testing done:
Verified that /var/lib/cni/results was cleaned up on reboot:

# journalctl -b |grep results
Feb 21 19:53:25 localhost systemd-tmpfiles[1010]: Running remove action for entry R /var/lib/cni/results
Feb 21 19:53:25 localhost systemd-tmpfiles[1010]: rm -rf "/var/lib/cni/results"
Feb 21 19:53:25 localhost systemd-tmpfiles[1010]: Running create action for entry R /var/lib/cni/results

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

The network device configurations referenced in the results do not
persist across reboot, so the cache isn't useful. Malformed or empty
files can also cause errors that interfere with subsequent operations
on pod sandboxes.

Signed-off-by: Ben Cressey <bcressey@amazon.com>
@bcressey bcressey merged commit 6c3b946 into bottlerocket-os:develop Feb 22, 2024
50 checks passed
@bcressey bcressey deleted the cni-cleanup branch February 22, 2024 01:00
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

Successfully merging this pull request may close these issues.

3 participants