Comment 28 for bug 2026200

This breaks our command-line pack of an in-house extension, under Ubuntu 20.04.
Is there a way to do this using the confined run?

Our current unconfined run build command-line (please excuse legacy from years ago, eg --headless might be more appropriate now):

xvfb-run /snap/chromium/current/usr/lib/chromium-browser/chrome --user-data-dir=/tmp/ChrUnsnapped --class="ChrUnsnapped" --pack-extension=MyExt --pack-extension-key=MyExt.pem

This understandably gets libm GLIBC version errors with a core22 dependent chromium snap.

Trying with confinement and --headless (and files moved to a subdirectory of /home/<user>):
user@host:~/tmp/ChromeExtensions$ /snap/bin/chromium --headless --enable-logging=stderr --pack-extension=MyExt --pack-extension-key=MyExt.pem
[0726/200919.476268:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[0726/200919.543209:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.

user@host:~/tmp/ChromeExtensions$ echo $?
0

Sadly no .crx comes out that I can find.