Skip to content

[BUG] Missing UMASK config #127

Description

@quadcom

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

ENV vars is either missing an entry for UMASK or it is not being applied correctly. Files created by the container are receiving incorrect permissions, impairing other containers and the host file system's ability to manage files. Processed file DLs using Lidarr applied permissions are 664 instead of 666/777.

Expected Behavior

Provide UMASK as a functional ENV var so that container processes create files with correct permissions.

Steps To Reproduce

Start-up logs show that the correct PUID and GUID are being applied. But this is not sufficient for correct file/folder permissions. Especially for Unraid systems.

Environment

- OS:Unraid
- How docker service was installed: Presinstalled and maintained by Unraid developers.

CPU architecture

x86-64

Docker creation

Unraid app template.

Container logs

,,,
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support the app dev(s) visit:
Lidarr: https://opencollective.com/lidarr
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    99
User GID:    100
───────────────────────────────────────
Linuxserver.io version: 3.1.2.4938-ls242
Build-date: 2026-03-30T02:57:40+00:00
───────────────────────────────────────
    
[custom-init] No custom files found, skipping...
,,,

Activity

  1. github-actions commented on Apr 5, 2026

    @github-actions

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

  2. aptalca commented on Apr 5, 2026

    @aptalca
    Member

    UMASK is already accepted as an env var, as explained in the readme.

    However, apps don't always respect umask, and *arrs usually have their own permission settings in their gui.

  3. LinuxServer-CI commented on May 5, 2026

    @LinuxServer-CI
    Collaborator

    This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

  4. moved this from Issues to Done in Issue & PR Trackeron Jul 5, 2026
  5. LinuxServer-CI commented on Aug 4, 2026

    @LinuxServer-CI
    Collaborator

    This issue is locked due to inactivity

  6. locked as resolved and limited conversation to collaborators on Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions