os VS pms-docker

And in the end we got a screenshot of a kernel-dump when we moved some nodes to VMs, which led us to this

I wonder if that's a job for rancherOS since everything in rancherOS is a docker container, https://rancher.com/docs/os/v1.x/en/ . Or is there some better compact OS?

The closest I can think of is the docker. If OP likes docker in their docker then they can start with RancherOS.

RancherOS 2.0.0 alpha01 was out 2 days ago : https://github.com/rancher/os/releases/tag/v2.0.0-alpha01

Was it RancherOS?

> RancherOS is the smallest, easiest way to run Docker in production. Every process in RancherOS is a container managed by Docker. This includes system services such as udev and syslog. Because it only includes the services necessary to run Docker, RancherOS is significantly smaller than most traditional operating systems.

https://rancher.com/docs/os/v1.x/en/

The nodes are thus totally neutral now. As a result, their templates are greatly simplified, and they can now easily be managed in an immutable way. This new paradigm opened the way to new Operating Systems specialized for container orchestration, such as CoreOS or RancherOS, whose life cycles are meant to be managed with an immutable workflow.

For this example, I'll be using a VPS on DigitalOcean running RancherOS with 2 CPUs and 2GB RAM. RancherOS a lightweight OS designed for hosting containers. If you'd prefer to use another distribution, you'll need to make sure Docker Engine is installed. Instructions for installing Docker Engine can be found in the Docker documentation. Any cloud provider will work just fine but I'd suggest the specs above as minimums.

Edit: here’s a link : https://github.com/rancher/os/issues/3000

When you say RancherOS do you mean "using Rancher" or do you also mean using RancherOS for your k8s nodes?

From what I can tell Plex can't see /dev/dri at all, as I get 45-plex-hw-transcode-and-connected-tuner: exited 0. in the logs which according to the source code means it did not see an existing device. Going into the container shows there isn't a /dev/dri folder at all though it does exist on my local machine.

I originally started using Docker because I wanted to run WireGuard alongside Pi-Hole and knew I would be wanting to add other containers and Docker's a good way to make everything play nicely. I originally wanted to install WireGuard immediately alongside Pi-Hole but that got shelved. The Plex Docker container can't be installed on Pi OS, there is an Plex docker container tough which is also causing me problems. IE: every time I update PMS (which is apparently a lot) it recreates the container, in addition to a lot of install errors.

I have a Raspberry Pi 4 8 GB Extreme running 64-bit Pi OS with Docker and Portainer. I'm trying to deploy the following image: https://github.com/plexinc/pms-docker. I'm creating a stack and then using a docker-compose file.

From what I can tell, there's even an official repository, and github repository.

Found it. The Docker container has a health check script. This script runs every 5 seconds. You can see this in the Plex console. Filter on "/identity".

The issue seems to be more that the container I'm trying to run is trying to chown a directory and runs into "Operation not permitted" issues. Specifically, this script is being executed and is failing, no matter which combination of user/namespace commands I am feeding it.

This looks like the official docker. Look through that and make sure you are using the correct docker.

So I'm run Plex server on my OMV server in docker container (this)[https://github.com/plexinc/pms-docker]. And my quality settings in win app looks like this (Show all do nothing)

The closest I can think of is the docker. If OP likes docker in their docker then they can start with RancherOS.