Best posts made by scottalanmiller

If you want to use Castopod, you almost certainly want to connect it to an S3 bucket. But the documentation on the site is missing a couple critical elements. The bucket must be specified and the format of the host needs the header. Here is an example configuration from the end of the .env file.

media.fileManager="s3"
media.s3.endpoint="https://s3.us-east-001.backblazeb2.com"
media.s3.bucket="bucketname"
media.s3.key="mykeyID"
media.s3.secret="mykeySecret"
media.s3.region="us-east-001"

This took some tracking down. The media.s3.bucket is absolutely critical, but does not appear in the documentation. The https:// I'm told is required as it prefixes bad data without it.

Turns out it is an App Armor restriction that Unity hasn't mentioned anywhere in their documentation even though we are at LEAST two releases into this problem. The fix is simple, but should be part of the install docs.

This is the error for the search engines:

No usable sandbox! Update your kernel or see Chromium Docs - Linux SUID Sandbox Development 48 for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

To Test:

sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

And then for the real fix: /etc/sysctl.d/unity.conf

kernel.apparmor_restrict_unprivileged_userns=0