Issues when running VS Code devcontainer as Sysbox

This issue only happens if I use debian:bullseye as base, and I copied and pasted all the contents from https://github.com/nestybox/dockerfiles/blob/master/ubuntu-focal-systemd/Dockerfile in order to install systemd in the debian:bullseye image.

I created a repository with the contents I used, it can be reproduced that way:

• https://github.com/felipecrs/sysbox-devcontainer.git

Funnily enough, if I take the exact same image which VS Code uses and use docker run on it, it works fine.

The command for testing is:

sudo sysctl kernel.dmesg_restrict=0

Although it requires the following patch on sysbox-fs first:

• https://github.com/nestybox/sysbox-fs/pull/77

Demo:

https://user-images.githubusercontent.com/29582865/199137480-c1a61644-54e2-4c18-ae22-19cecd921ca7.mp4

PS:

• If I use ubuntu-jammy as base, it works fine always
• It's totally understandable if your prefer not to spent time investigating this issue. I spent several hours on it, and could not get further. I'm opening this issue so I can at least document this "limitation", or simply acknowledge it for future reference. Thus, feel free to also close it if you prefer to keep the backlog clean.

Start with the reproducer in felipecrs/sysbox-devcontainer and compare the VS Code devcontainer path with the working docker run path, using debian:bullseye and the systemd Dockerfile contents described here. Apply the prerequisite sysbox-fs PR 77 when testing the sudo sysctl kernel.dmesg_restrict=0 command; done means identifying the cause, fixing the behavior, or documenting the Debian limitation.