containerd-1.6.6-4.ph4.x86_64 breaks the Docker container runtime

Describe the bug

The latest containerd package (1.6.6-4.ph4.x86_64) appears to break networking in some containers.
When testing this package with couchdb 2.3.0 the container exhibited a large consumption of RAM and never opens the default TCP listen port 5984.

Reproduction steps

A fresh install of Photon 4.0 starts with containerd-1.4.4-8.ph4.x86_64 - all containers work as expected using this package.
After performing a tdnf update, the following packages are installed (they all depend on each other for installation):

• containerd-extras-1.6.6-4.ph4
• containerd-1.6.6-4.ph4
• runc-1.1.4-2.ph4

After rebooting Photon 4, run the following command to test a couchdb container:

systemctl start docker && CONTAINER=$(docker run -d --rm couchdb:2.3.0) && docker exec -it ${CONTAINER} /bin/bash -c "apt update ; apt -y install net-tools && sleep 5 && netstat -pantu" && docker rm -f ${CONTAINER}

Note that the couchdb process never starts listening on the default port 5984 (as would be expected). Reverting the packages back to the following versions resolves the issue after a reboot:

• containerd-1.4.4-8.ph4.x86_64
• containerd-extras-1.4.4-8.ph4.x86_64
• runc-1.0.0.rc93-5.ph4.x86_64

Expected behavior

Couchdb containers should begin to listen on port 5984 after a tdnf update.

Additional context

No response

Start by reproducing the failure on Photon 4 with containerd 1.6.6-4.ph4, runc 1.1.4-2.ph4, and the provided docker run command, then compare it with the older package versions. Check whether the CouchDB container reaches TCP port 5984 and investigate the reported RAM growth. Done means the updated runtime starts CouchDB and exposes port 5984 normally.