Closed cy-zheng closed 4 years ago
BTW, do you have any plan to implement a cri executor, which talk with the runtime using standard cri api? That would be more graceful and compatible with different cri backend.
Would you like to submit a PR to fix?
@cy-zheng looks like you have the right idea for the fix. We'd love your assistance with this!
@cy-zheng looks like you have the right idea for the fix. We'd love your assistance with this!
OK. I would create a PR for this issue :)
Summary
What happened/what you expected to happen?
When I use pns executor with containerd runtime,
argo stop
couldn't stop workflow pod successfully. The root cause is that containerd cgroup structure is different from docker, and pns executor failed to parse container id from /proc/{pid}/cgroup file.Diagnostics
What Kubernetes provider are you using?
bare metal v1.13.12 with containerd at v1.3.6
What version of Argo Workflows are you running?
v2.11.3
/proc/{pid}/cgroup in docker container
/proc/{pid}/cgroup in containerd
Proposal
Add code below to https://github.com/argoproj/argo/blob/v2.11.3/workflow/executor/pns/pns.go#L407
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.