> at this stage Plexamp is waiting for the claim token input

Note: arm-461 is for Plexamp version 4.6.1 arm 32 bits Image: /zonywhoop/plexamp-headless-docker: arm-461 Create /data/docker/plexamp/docker-compose.yaml.> This is to match local owner ID with docker Plexamp ID (if I understood well) Change ownership: chown 1001:100 /data/docker/plexamp.Some may be incomplete or incorrect, please shout in such case! Whenever a new Plexamp version is available, downloading and extracting it in place of the running one are the only required steps.Ĭhristian Brückner, here are the notes I took. Terminal: To run Plexamp as a service, a few other steps have to be performed.Browser: Access Plexamp UI at to fine tune its configuration and play some music.Terminal: Enter the token, Plexamp should now be running, using the default sound card.Browser: get the claim token at (you'll need to sign in Plex if not done already).

At this stage you have to provide a 'claim token' used to claim your Plex Media Server associated to your Plex account

Terminal: Untar Plexamp archive in the root home directory.

Terminal: Download Plexamp archive file in the root home directory.

Terminal: Install required version of Node.Js (12 or 16 from Plexamp 4.6.0 (still in beta)).

Terminal: Install Nove Version Manager (NVM).

Terminal: Open/ssh a terminal session against HFBOS.

Without going into much details for now, here are the steps I used to install it in HFBOS (prerequisite: HFBOS installed and tested, ssh enabled in HFBOS, Valid Plex account + Plex Pass (TBC), Web browser): Unfortunately I don't think a docker can easily do the job as each Plexamp instance is linked to a Plex account that is configured during the initial installation, unless there is a 'docker' way to manage this scenario?Īlso, a docker layer may have an impact on the performance in RPI without enough memory/cpu.

Plex amp