docker-handbrake VS distrobox

Handbrake (https://github.com/jlesage/docker-handbrake) - Similar to QT bittorrent, nice to have a spot where I can dump my video files and it has tools to monitor new files dropped in and custom formats.

I would highly suggest that you use https://github.com/jlesage/docker-handbrake/blob/master/README.md

Do you use docker? You could use the ripper container and use handbrake container. You’d set the output directory of ripper to be the handbrake input directory. Just put the disk in the drive you have setup and ripper will do it’s thing. After it’s done handbrake will detect a movie and encode it using your settings.

Very new to docker - although quite techy. I am guessing I missed permissions or something somewhere. I have set up Handbrake https://github.com/jlesage/docker-handbrake within Docker following this guide: https://www.youtube.com/watch?v=E6HgHsxdWIo I can access it via port5800, however when I go to add a file/folder the pop up goes to "storage" if I go to "Other Locations" I can see the folder I specified during set up, but then I get "Cannot Read contents of GoProToSort" "Error opening directory. Permission Denied"

But when jlesage/handbrake launches, even if you manually specify uid:gid 1000:1000, there are permission errors:

It sounds like you missed the x11vnc part of this. You connect into the container using vnc, not x11. If you want to see a working example of a gui app running successfully in docker, check out https://github.com/jlesage/docker-handbrake

There isn't a magic setting or anything, and honestly, I don't recommend tdarr, mostly because you can do all the same stuff it does with a bash script and jlesage's handbrake container (or just handbrake outright).

My NAS/home server is a NON-COREBOOT HPE-Proliant-Gen10 microserver I have some details here. 24G ECC, 24TB RAIDZ-2. I am running docker containers for Makemkv, Handbrake, Filebot, Jellyfin, Gitea, TinyTinyRSS, Bitwarden, Samba (readonly for Kodi running on an Nvidia Sheild TV), Restic backup, Nextcloud, PFELK (router stats) and a weather forecast app I run on an old Nook in a picture frame. It isn't fast but it doesn't need to be for my needs.

Regarding the stability issue on a dev machine - you may be interested in playing with one of the immutable-os distros, such as SilverBlue (fedora based).

The high-level take-away is you can't break your actual OS since it's root filesystem is read-only, and you use "pet" containers (on docker, podman, whatever) to do your work in. Applications are either sandboxed via Flatpak, or installed/run inside your pet containers. If your pet container dies, you cry about it for a moment, and when you're ready you get a new one - your actual os and other containers remain unaffected.

I use distrobox[1] to create/run the pet containers.

[1] https://github.com/89luca89/distrobox

Distrobox is a tool that enables us to try Linux distro CLI, including their package manager. This requires a containerization tool (e.g., Docker). In Windows, this can be achieved using WSL (Windows Subsystem for Linux)

I use containerized versions of things, ubuntu and chainguard images mostly.

You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...

https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...

Yes, you can do that but I've seen others use something like distrobox to run linux inside of SteamOS: https://github.com/89luca89/distrobox/blob/main/docs/posts/steamdeck_guide.md

For such cases you might use something like this: https://github.com/89luca89/distrobox

Btw #3: Depending on what the user is trying to accomplish, e.g. maybe to make WSL(2) itself more of a "subsystem" than a "container engine", using something like Distrobox or nsbox.dev can be a good idea (along with Docker or Podman in Distrobox's case; the other one uses systemd-nspawn).

1. Find here in "Containers Distros" section the distro image that you want to install ("Toolbox" versions are better because they are configured for Distrobox) and get it URL: https://distrobox.it/compatibility/#containers-distros 2. Use that URL to create Distrobox: distrobox create -i registry.fedoraproject.org/fedora-toolbox:39 -n fedora_1_39 3. Enter Distrobox fedora_1_39: distrobox enter fedora_1_39 4. You are already in Distrobox console. Look at the name in console, it should be include the container name. 5. To exit Distrobox: exit 6. If you run: distrobox list you will see all distroboxes on the system. You will also see that distrobox that we exited is still running. 7. To stop distrobox use commands: distrobox stop fedora_1_39