The container will refuse to start and provide some useful information
to the user:
```
docker-jitsi-meet-jibri-1 | cap[cap_sys_admin] not permitted
docker-jitsi-meet-jibri-1 | Required capability SYS_ADMIN is missing
docker-jitsi-meet-jibri-1 | [cont-init.d] 10-config: exited 1.
docker-jitsi-meet-jibri-1 | [cont-finish.d] executing container finish scripts...
docker-jitsi-meet-jibri-1 | [cont-finish.d] done.
docker-jitsi-meet-jibri-1 | [s6-finish] waiting for services.
```
If the container was staryed without a /dev/shm of at least 2GB
(defaults to 6MB in Docker) Chrome will behave erratically or crash.
Catch this with a tiny binary and make the container fail to start.
Ref: https://github.com/jitsi/docker-jitsi-meet/issues/1653