Temporarily use containerd from Docker packages

[hakman]

Docker builds the containerd binaries differently than containerd does.
This makes possible some things like enabling SELinux, which otherwise as described in #9334 (comment).

Using containerd from the docker packages should ensure better compatibility.

[justinsb]

My knee-jerk reaction is that we should stick to the community packages; I was very happy with the work you did that reduced our dependencies on the docker.com packages, as they've bitten us repeatedly in the past.

Is there a containerd issue tracking the selinux issue?

[hakman]

@justinsb I was quite happy with that also and would like to keep the same direction in the future.
I think the issue here is containerd/containerd#4183, which was not cherry-picked to release branches.

[hakman]

@justinsb I created some PRs to address this in future releases, and change again to the community packages. Do you think it's ok to switch to Docker packages until then?
containerd/containerd#4318
containerd/containerd#4319

[hakman]

Both PRs for containerd were accepted and next release will be built with SELinux support.
As is, this change will just use Docker temporarily and should be reverted once a new version of containerd is released.

@justinsb any objections?

[rifelpet]

As discussed during office hours, we decided this is acceptable for a temporary solution until the next containerd release 👍
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman, rifelpet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rifelpet]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment