wondershaper VS bubblewrap

this article will help you limit your network bandwidth using wondershaper tool !!

Yes, you can do this via Wondershaper (https://github.com/magnific0/wondershaper) for example: https://vitux.com/how-to-limit-network-bandwidth-in-ubuntu/

I’d like to play with the device’s bandwidth for debugging purposes. I saw wondershaper but it seems to have issues on Jetsons.

For super simplification (bandwidth + shaping) wondershaper has a wrapper script - https://github.com/magnific0/wondershaper/ tc has a lot of depth to it depending on what you are trying to accomplish, unfortunately besides going through the man page and trying stuff I don't really have anything else to give you.

[1]: https://github.com/magnific0/wondershaper/blob/master/wondershaper

To quote from the readme:

You better never try something like the wondershaper with ifconfig ...

Nothing nix specific but you may be interested in https://github.com/containers/bubblewrap

Recently, I came across Chainguard and wrote the article How to build Docker Images with Melange and Apko. As a fervent supporter of Kubernetes and GitLab CI, I was eager to experiment with building images using Melange in this particular setup. GitLab's shared Runners work seamlessly with Bubblewrap, eliminating the need for additional configurations. This post is intended for enthusiasts like myself, interested in hosting their own Kubernetes Runners and leveraging the Kubernetes Runner Type of Melange.

```

This is basically manually invoking what Flatpak does:

https://github.com/containers/bubblewrap

This is also useful for more than just security. E.G., you can test how your app would behave on a fresh install by masking your user configuration files. I personally also have a tool that uses it to basically bundle all dependencies from an entire Linux distribution in order to make highly portable AppImages— Been meaning to post that, will get around to it eventually maybe.

The flags above should hide your user data (`--tmpfs`), disable network access (`--unshare-all`), hide/virtualize devices and OS state (`--dev` and `--proc`), and make the rest of the root filesystem read-only (`--ro-bind`­— Including the insecure X11 socket in `/tmp`, which you might want to expose for GUI apps).

Check them against `bwrap --help`; I might have omitted one or two more things you'd need.

While trying to find out more comparison information, found this light on details issue:

https://github.com/containers/bubblewrap/issues/81

It mentions nsjail and minijail.