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.

Sign up for GitHub

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

Jump to bottom

[FR] Allow to define containerd.sock path #171

Closed
bkupidura opened this issue Apr 25, 2022 · 0 comments
Closed

[FR] Allow to define containerd.sock path #171

bkupidura opened this issue Apr 25, 2022 · 0 comments
Assignees
@senthilrch
Labels
feature New feature
Milestone
v0.10.0

Comments

@bkupidura
Copy link

Currently containerd.sock path is hardcoded (/run/containerd/containerd.sock).

This will cause image cleanup Job to faild everytime on environments with different path (e.g. k3s).

containerd.sock is located in /run/k3s/containerd/containerd.sock for k3s, probably other locations are also possible with different k8s distributions.
@senthilrch senthilrch added the feature New feature label Apr 27, 2022
@senthilrch senthilrch added this to the v0.10.0 milestone Apr 27, 2022
@senthilrch senthilrch mentioned this issue Oct 20, 2022
Merged
@senthilrch senthilrch self-assigned this Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@senthilrch senthilrch

Labels
feature New feature
Projects
None yet
Milestone
v0.10.0
Development

No branches or pull requests
2 participants
@bkupidura @senthilrch