pms-docker VS watchtower

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.

GitHub issue for podman support, here: https://github.com/containrrr/watchtower/issues/1060

compose-updater (python, api-service) – a project for updating the version of a docker image from CI in a closed infrastructure. I didn't find anything ready to solve this task. There is watchtower, but it's more about keeping up-to-date docker images, rather than updating a specific one, and also I couldn't run it with ECR repos – the author made a super minimalist image in which I couldn't enter through sh to debug. The second alternative is umputun/updater, but it's more about running different shell commands through a webhook. I chose Python because I didn't find a Rust crate for Docker API (most likely it exists, I just didn't understand which one is really good). Score: – (I didn't promote the project anywhere, I use it for my own purposes for now).

WatchTower is one of my favorite projects because it is super useful, and it was also my start in DevOps. WatchTower is a containerized application that monitors your running containers, and will automatically update your images when a newer version is available. Pretty simple, but super useful if you want to run your own infrastructure. Awesome learning experience, and it has over 18k stars!

Interesting- my first time reading about Kamal. I personally used watchtower (https://github.com/containrrr/watchtower) to check for and deploy container updates from the GitHub Container Registry and push new images there from Actions. I also used OpenTofu to automate the VPS provisioning in GH Actions.

For a single server I’d rather have one config management system - Chef/Ansible/… - and just have that set up docker & nginx, rather than have config management set up Kubernetes, and then also need to write Kubernetes manifest YAML files in addition to my config management thingies.

On my home server I use Chef. I have a recipe for each service that sets up a docker container plus an NGINX config that does the TLS and port mapping stuff. To handle container updates I run Watchtower (https://containrrr.dev/watchtower/) which pulls and then restarts my containers when I send a POST.

Deploys are super easy, just docker build, docker push, curl -h $DEPLOY_TOKEN $DEPLOY_URL.

don’t need anything complicated for rollback, just retag and curl again.

Related: https://github.com/containrrr/watchtower