Skip to content

Maintainerr #2041

Closed
Closed

Description

@MickLesk

Name of the Script

Maintainerr

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 supported

📋 Script Details

Maintainerr

Activity

  1. github-actions commented on Jul 20, 2026

    @github-actions
    Contributor

    The Maintainerr script is ready for testing:
    bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/maintainerr.sh)"
    Complete the setup wizard via the web interface on first access, then connect Maintainerr to your media servers (Plex/Jellyfin/Emby) and to Radarr/Sonarr/Seerr.

    Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

  2. yourfate commented on Jul 30, 2026

    @yourfate

    Install fails on my machine, log is attached. The output from yarn that actually fails is:

      ✔️  Setup Node.js 24
      ✔️  Deployed: maintainerr (3.20.1)
      ⏳   Building Maintainerr (Patience)Preparing yarn@4.11.0 for immediate activation...
    ➤ YN0000: Successfully set enableTelemetry to false
    ➤ YN0000: · Yarn 4.17.1
    ➤ YN0000: ┌ Resolution step
    ➤ YN0000: └ Completed
    ➤ YN0000: ┌ Post-resolution validation
    ➤ YN0060: │ better-sqlite3 is listed by your project with version 13.0.2 (p87dca6), which doesn't satisfy what typeorm requests (^12.0.0).
    ➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
    ➤ YN0000: └ Completed
    ➤ YN0000: ┌ Fetch step
    ➤ YN0000: ⠼ ==============================================================------------------
      ✖️  in line 39: exit code 39 (Command failed with exit status 39): while executing command  yarn install --network-timeout 300000
    
    

    Seems like it might have been oom-killed.

    install-03b3c6ba-combined.log

    I'm trying again with more disk and more ram, to see if that helps.

    Update: Changed it to 4 cpu, 8GB ram, 32GB disk, and the install worked.

  3. yourfate commented on Jul 31, 2026

    @yourfate

    Another discovery: the script says it deploys version v3.20.1, however, it seems it has insatlled the develop version of Maintainerr, not a tagged released.

    Image
  4. MickLesk commented on Jul 31, 2026

    @MickLesk
    MemberAuthor

    thats because the tarball doesnt contain the version number, we need to write it fix in source code

  5. GingerHz commented on Aug 3, 2026

    @GingerHz

    I attempted to install via the script and see the following error:

    /dev/fd/63: line 1441: media;arr;cleanup: syntax error: invalid arithmetic operator (error token is ";arr;cleanup")

    Image

    I am unsure how to resolve this error so I am unable to install via the provided script. I thought it may be related to the tagging for the container so I removed the tags during config and even tried keeping parts of the tags and that did not seem to make any difference. Any ideas how I can resolve this so I can install this LXC?

  6. MickLesk commented on Aug 3, 2026

    @MickLesk
    MemberAuthor

    Run advanced Install an remove the Tags, i think their is the issue located. I only can take a Look tomorrow, the Script isnt from me

  7. 4 remaining items

  8. Naeloran commented on Aug 21, 2026

    @Naeloran

    Working good so far. It did have a moment where it stalled during initial setup while confirming network connectivity. This didn't happen again after I ran the script on a different node and raised the boot disk size to 32 gigs. No issues noted so far.

  9. znarfm commented on Aug 22, 2026

    @znarfm

    working well with default install.
    failed on me when I customized it.

  10. MickLesk commented on Aug 22, 2026

    @MickLesk
    MemberAuthor

    What fail? @znarfm

  11. znarfm commented on Aug 22, 2026

    @znarfm

    What fail? @znarfm

    my bad. just it was an Out of Memory error on my end.

    I customized the LXC RAM down to 1 GB, which caused yarn install to fail during the build step. Default RAM settings handle the build fine. Just wanted to know if RAM can be lower than 8 GB?

  12. Dannurz commented on Aug 22, 2026

    @Dannurz

    Worked fine :) Thanks you!

  13. github-actions commented on Aug 24, 2026

    @github-actions
    Contributor

    A PR has been created for maintainerr: community-scripts/ProxmoxVE#16716

  14. SemperEnim commented on Aug 24, 2026

    @SemperEnim

    also worked fine for me. migrated from a docker install to the LXC with no issues.

  15. T-Gander commented on Aug 25, 2026

    @T-Gander

    Appears to be working for me. Switched over from an OCI image with no issue.

  16. michelroegl-brunner commented on Aug 25, 2026

    @michelroegl-brunner
    Member

    Merged with #16716 in ProxmoxVE

  17. github-actions commented on Aug 25, 2026

    @github-actions
    Contributor

    Files deleted with PR #2219

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

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions