Hi @mgiessing. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 26s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 14s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 23m 14s (non-voting)

@mgiessing can you please verify the binaries from this release test run? https://github.com/dmcgowan/containerd/releases/tag/v1.7.0-alpha.ppctest

Signed-off-by: mgiessing <marvin.giessing@gmail.com>

Also, please sign the commit using your real name rather than username (https://github.com/containerd/project/blob/main/CONTRIBUTING.md#sign-your-work). Ideally configure it in git so we don't have to add a record in mailmap.

@dmcgowan Thanks! I followed https://github.com/containerd/containerd/blob/main/docs/getting-started.md#option-1-from-the-official-binaries to install & verify the binaries from the release test run.
Furthermore I ran the integration test (make integration) which also succeeded

[...]
time="2022-04-26T17:19:54.315837088-04:00" level=info msg="Event monitor stopped"
time="2022-04-26T17:19:54.315885987-04:00" level=info msg="Stream server stopped"

ok  	github.com/containerd/containerd/integration/client	334.186s

Signature is also updated to my real name, but I guess that is not applied retroactively to previous commits.

Signature should also be updated by now - if you need anything else let me know.
Thanks!

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 46s (non-voting)
• containerd-test-arm64 : SUCCESS in 5m 17s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 24m 23s (non-voting)

Any idea when this will produce the package in the release and can this be cherrypicked into release/1.6 branch as well?

Yeah, I would appreciate that as well!

@estesp Is it possible to have a cherrypick of the ppc release into 1.6?
If not - is there a rough estimate when 1.7 will be released?
Thanks!