Snap Version#: 1.19.2.2737-b69929dab
Linux Kernel#: 5.3.0-1023-raspi2 AND 5.4.0-1008-raspi
Hardware#: Raspberry Pi 4B (4GB of RAM)
OS#: Ubuntu Server 18.04.1 AND Ubuntu Server 20.04
Hi there, I am trying to set up a Plex Media Server on my Raspberry Pi 4. I used the .deb package before and had no issues whatsoever. I am now trying to install it as a snap, considering arm64 is now a supported architecture. I have used PMS on snap many other times on different architectures and had no issues with it.
When I try on my Raspberry Pi 4 the installation complete successfully but the service dies almost immediately due to a permission error: apparmor throws an error.
I have tried with two different Raspberry Pies running both different linux kernels and different Ubuntu server versions. I have tried to perform a fresh install of the operating system but the problem remains unaltered.
I have attached a syslog showing the apparmor error.
Any idea on how to proceed from there?
Why use the snap package when native already works? Both will update automatically; both have your metadata in /var/lib/plexmediaserver. The only difference in control is use of the snap executiveversussystemctl`
Plex won’t update automatically on arm64 even with the conventional .deb file because Plex has yet to release an official repository. One still needs to download a new .deb file for each new version.
Anyway this is not what I have asked. I know that the conventional deb package works, I am interested to make it work on a snap (Also, snap still uses systemctl like any other service on linux )
The fact that APPARMOR denies it, means that the snap package has not been configured correctly during the compilation. I just thought that reporting it here would be beneficial for future release
This is not accurate. When you install the PMS package, a repository is added under /etc/apt/sources.list.d/plexmediaserver.list. If you edit this file, uncomment the repository, and add the signing key (the command is listed in the file) you can update PMS using the usual method: sudo apt update && sudo apt upgrade -y
I just did this on my Pi 4 running Ubuntu Server 20.04 and it works as expected.
That’s fair. I just wanted to make sure you were aware that there is indeed a Plex-supported method of keeping your arm64 Pi up to date with the native package.
I will look into the SNAP package but if only one person appears to be reporting it, I’m not sure this is a SNAP-wide problem?
Help me understand please?
Plex builds & maintains the SNAP package.
The normal DEB package cannot be used to update a SNAP package because the destination file locations and control mechanisms are different.
The only cross-methodology capability I’ve been able to provide at this point is updating a Docker container with the native DEB because Docker containers are built from a native DEB configuration.
I tested the snap package as well and saw the same behavior: Attempting to start it resulted in failure, with the permissions errors referenced above. However, I don’t personally use the snap package normally and wouldn’t have noticed had @turux not reported it.
That would indeed be a neat trick; hopefully no-one expects that.
my HW is raspberry pi 4 (4GB if matter) and ubuntu 18.4.1. Using the snap for arm64 it fail to start.
Even the latest snap version: 1.19.2.2737-b69929dab
Thank you @ChuckPa
FYI, I did a test on my old Pi 3B+ with ubuntu 18.04 to have a test on different HW, but I got the same issue using snap pms package.
Mate, far from me from asking any of that! This is not an emergency and obviously there are plenty of workarounds. I just noticed a bug and thought it would be good to report it!
Thanks for your time! Stay safe in these challenging times
Thanks for trying this @marcello_f_icloud_com! Seems to be a problem linked with the arm64 architecture. It would be nice to test it on another armv8 device that is not a raspberry pi
(Also, snap still uses systemctl like any other service on linux 
)
