busybox VS unpackerr

A majority of routers are already based on the Linux kernel. Many are just BusyBox. The most common Linux firewalls are iptables and nftables. With the latter being the most popular one due to being around longer. They are really fine grained and powerful.

As Busybox DockerFile does not contain any EntryPoint(https://github.com/docker-library/busybox/blob/master/musl/Dockerfile), so arguments specified in the kubectl command will only be used, so the command will look like:

https://www.kernel.org/doc/Documentation/arm64/booting.rst This was my guiding light for a project a while back. It describes what Linux expects "time zero" looks like for the system; whatever operating system is going to boot needs that kind of contract between the boot environment and its own entry point. You can develop a lightweight linux-based OS with that document and a package like https://busybox.net/

UUTILS, musl libc, BusyBox , etc.

For libc, we have musl as an alternate implementation. For most coreutils, we have busybox and the BSD coreutils. For desktop environments, you can use something like xfce.

I just found a project called Unpackerr which sounds like an absolute dream for me, it would fix my unpacking issue. I have Truenas Core installed, and found a guide for installing on Truenas scale here. During the container configuration, you need to set up some environmental variables.. is this possible to do on Truenas Core?

nope, unpackerr works across multiple systems: https://github.com/Unpackerr/unpackerr

Unpackerr

For anyone reading this, Unpackerr is by far the better solution to packed torrents.

I don't, that's what unpackerr's for.

You can run Sonarr, Radarr, Flaresolverr(if your tracker is behind Cloudflare protection), Deluge, Unpackerr, and Overseerr on Windows.

Also, you can use unpackerr

Check out Unpackerr. I haven't had any issues with extraction since using it