Podman tests fails in CI due to restricted permissions in podman service started by non-root user

[consideRatio]

• All tests were passing Aug 2 2022
• podman test started failing Aug 9 2022

The podman test failure remains after #485 that solved some other failures, but is tolerated with continue-on-error: true on the step running podman tests.

The failure is that the podman system service that starts containers, and is started by the non-root user, doesn't have sufficient cgroup permissions to constrain CPU usage etc in the started containers I think. This is described in podman's troubleshooting docs.

docker.errors.APIError: 500 Server Error for http+docker://localhost/v1.40/containers/65b02b7e1a0aa53a877e961e1f65b3af4be0c89c20fe4d9bc4d2bc619f816002/start: Internal Server Error ("the requested cgroup controller `cpu` is not available: OCI runtime error")

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉