Skip to content

Prioritize SNAP_CURRENT in containerd paths #4710

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

Merged
merged 1 commit into from
Oct 22, 2024
Merged

Conversation

berkayoz
Copy link
Member

The wrong priority in path leads to issues with containerd-shim binary trying to be called from a previous revision that is not installed anymore. Prioritizing $SNAP_CURRENT paths makes sure this path always exists and points to the latest binary.

Fixes #4691

Copy link
Contributor

@bschimke95 bschimke95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, we can merge this after 1.31 branch out

@berkayoz berkayoz merged commit c77311b into master Oct 22, 2024
10 of 11 checks passed
@berkayoz berkayoz deleted the KU-1784/shim-path-fix branch October 22, 2024 15:14
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.

Microk8s restart during snap refresh did not remove pods
2 participants