lv2 VS firejail

The LV2 audio plugin standard[0], and related stuff like the Atom format[1] used to feed arbitrary data between plugins in realtime.

[0] https://lv2plug.in/

Not all VSTs will work on Linux (just as not all VSTs work on Mac). Many open-source plugins are in the open LV2 format instead.

LV2 homepage

This is extremely cool. Many years ago I started and abandoned a similar kind of thing. The plan was to have support for LV2[1] plugins, so you'd get something like a Mod Duo[2] (itself very cool), but like this in that'd boot fast and have super low latency.

[1] https://lv2plug.in/

[2] https://moddevices.com/products/mod-duo/

Nice though nothing about Turtle or LV2

https://www.w3.org/2007/02/turtle/primer/

https://github.com/lv2/lv2/wiki

Folk can check out https://github.com/lv2/lv2/wiki for more info

https://github.com/lv2/lv2/wiki for more into LV2 itself

bubblewrap is designed as a low-level too. There is nothing quick and dirty about it. It disallows everything by default and you have to be explicit about what you want to share with the host. If your application needs complex permissions/resources, then you will need to have a complex bubblewrap command line.

Once you have figured out which permissions/resources you need for a given program, you can wrap the command line invocation in a shell script.

If you want other people to do the work of defining permissions/resources, then have a look at firejail: https://github.com/netblue30/firejail

Firejail is cool: https://github.com/netblue30/firejail

Linux namespaces/cgroups but nowhere near as heavy as Docker.

I use it when I want to limit the memory of a Python script:

```

Firejail can also be a useful option, though no good if you're on Mac https://firejail.wordpress.com/

Uses the same Linux primitives as docker etc, but can be a bit more ergonomic for this use case

Firejail, Flatpak (which uses Bubblewrap under the hood), and Snap (which uses AppArmor) all use the same underlying technology: Linux namespaces.

This question comes up a lot, and has been answered here: https://github.com/netblue30/firejail/wiki/Frequently-Asked-...

TL;DR: Firejail has much more comprehensive features than Flatpak (Bubblewrap). Firejail also has more comprehensive network support, support for AppArmor and SELinux, and easier seccomp filtering.

Compared to Snap (which uses AppArmor), Firejail is compatible with AppArmor and again goes above and beyond with a lot of additional features.

Wonderful little tool, too bad you must chain various exec calling tools to get cgroups (a bit akin to `ionice ... nice ... cmd`) and Linux users namespaces can't allow UNIX sockets while preventing network access (I think?).

Migrated from Firejail when its complexity annoyed me too much and I hit https://github.com/netblue30/firejail/issues/3001 (Firejail doesn't like parens or brackets in --put/--get parameters) to a badly NIH version using bwrap and bash to have "profiles":

Firejail does this. The profile database is the two "profile" directories in https://github.com/netblue30/firejail/tree/master/etc

What do you mean by a Firefox container? Do you mean FireJail?