Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Ramdisk for logs lacking folder ownership for non-root user #419

Closed
1 task done
Zer0PointModule opened this issue Feb 3, 2025 · 4 comments
Closed
1 task done

Comments

@Zer0PointModule
Copy link

Is this a new feature request?

  • I have searched the existing issues

Wanted change

I have a small nitpick especially when it comes to using ram disks

Plex is rather spammy with logs and even with as much logging disabled as possible it still writes quite a lot to the log file, if someone were to mount a ramdisk to the logs folder (/config/Library/Application Support/Plex Media Server/Logs) that would reduce IO, but unfortunately the ramdisk has default ownership of root:root with 770 permissions.

It would be nice if on boot we would make sure the permissions are set correctly on this folder and if not change ownership, that way things would be easier for people preferring ram disks for their log folder.

Reason for change

Reduce disk usage while running plex as much as possible to conserve the lifetime of the disks that it uses.

Proposed code change

No response

Copy link

github-actions bot commented Feb 3, 2025

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@Zer0PointModule Zer0PointModule changed the title [FEAT] Additional folder ownership for non-root user [FEAT] Ramdisk for logs lacking folder ownership for non-root user Feb 3, 2025
@Roxedus
Copy link
Member

Roxedus commented Feb 3, 2025

You can set the IDs of tmpfs. https://docs.docker.com/engine/storage/tmpfs/#options-for---tmpfs

@Zer0PointModule
Copy link
Author

Thanks,

This is great for when you have full control over all docker options, I can manage with this and it will work indeed, however if you use wrappers around docker like for example synology / truenas / ... you don't always have access to configure this.

I understand this is extremely niche, but it would be a quality of life improvement to make sure it's chowned properly on boot of the container.

Which I thought it would do here:
https://github.com/linuxserver/docker-plex/blob/master/root/etc/s6-overlay/s6-rc.d/init-plex-chown/run

lsiown -R abc:abc \ /config/Library

But the ramdisk remains root:root

@j0nnymoe
Copy link
Member

j0nnymoe commented Feb 3, 2025

Realistically our main aim for support is using docker compose, which while those platforms you mention, all of them can run docker compose so I don't think we need to add anything.

@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants