/run seems not to have correct rights

Open
#457 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
docker
Domain
devops

Research direction

Start by inspecting how the container creates and permissions /run/plex-temp, then reproduce with docker restart plex using the latest image in Portainer. Compare the resulting permissions with the reported chmod 755 /run workaround and verify that Plex starts without the permission-denied crash.

Written by the indexing model from the issue text.

Description

invalid no-issue-activity
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

1.43.2.10687-563d026ea
in container bash:

# namei -om /run/plex-temp
f: /run/plex-temp
 drwxr-xr-x root root  /
 drwxr-xr-- root root  run
 drwxr-xr-x abc  users plex-temp

and running:
chmod 755 /run

fixed it

just for info: running the plex image in portainer under OMV

Expected Behavior

No response

Steps To Reproduce

docker restart plex
and the permissions are gone again

Environment
- OS:
- How docker service was installed:
CPU architecture

x86-64

Docker creation
just using the latest image creation in portainer
Container logs
Starting Plex Media Server. . . (you can ignore the libusb_init error)

libc++abi: terminating with uncaught exception of type std::runtime_error: Codecs: Initialize: 'boost::filesystem::status: Permission denied [system:13]: "/run/plex-temp"'

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.43.2.10687-563d026ea/PLEX MEDIA SERVER/4a79c970-997c-40ff-6dbcb9a5-eca347d1.
Dominant language
Dockerfile
Stars
1.4k
Forks
228
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxserver/docker-plex

All issues in linuxserver/docker-plex

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.