dockerspawner: JupyterLab O/S' launched by JupyterHub (i.e. by DockerSpawner) is causing cgroup-related issues such that podman(1) fails ...

Dear Friends:

I provide a very detailed background on this issue here, but that issue is closed (wrong repo) and I need assistance. Please read that question because it is what this issue here is about. (Thank you).

When JupyterHub spawns (via DockerSpawner) a JupyterLab container image, it is missing docker runtime attributes and/or O/S capabilities that allow RedHat’s podman(1) to work properly. Here’s a summary example, but complete information is available at the above URL:

jovyan@lCONTAINER$ mkdir -p ${HOME}/data.d/mariadb.d/var/lib/mysql

jovyan@CONTAINER$ podman run --events-backend=file --name mariadb01 \
   -p 3306:3306 -v ${HOME}/data.d/mariadb.d/var/lib/mysql:/var/lib/mysql:Z \
   -e MYSQL_ROOT_PASSWORD=**** -e MYSQL_DATABASE=db01 \
   -e MYSQL_USER=jdoe -e MYSQL_PASSWORD=**** -d docker.io/library/mariadb

Error: OCI runtime error: container_linux.go:370: starting container process caused:
process_linux.go:326: applying cgroup configuration for process caused:
no cgroup mount found in mountinfo

The above is not an issue when I spawn the identical container-image manually (again please see URL above for blow-by-blow walk-through), but it is a problem when JupyterHub spawns it via DockerSpawner. Please help me.

Thank you!