Upgrade containerd to include a fix for CRI issue #1280

[matlec]

Version:
k3s version v0.10.0-rc1 (ccb1d81)

Describe the bug
Since we upgraded from k3s 0.8.1, several pods (including the pods deployed by the official PostgreSQL helm chart) fail to run with the following error message:

Error: failed to create containerd task: OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \"sh\": executable file not found in $PATH": unknown`

To Reproduce
Steps to reproduce the behavior:

• use Helm to install PostgreSQL from stable/postgresql

Additional context
containerd Issue #3597 describes the original bug in containerd which got fixed by this pull request and cherry-picked to the 1.3 release branch.

Please bump containerd/cri to a revision that includes this fix. Thank you!

[mshade]

I can verify this bug is also present in k3s v0.9.1.

[davidnuzik]

I was able to also reproduce on v0.10.0-rc2:
Error: failed to create containerd task: OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \"sh\": executable file not found in $PATH": unknown

[davidnuzik]

Appears to be fixed with bump in containerd version in master.

[davidnuzik]

Fixed in v0.10.0 release.