Error Trying to Run Librenms in Docker Container on QNAP #532
Replies: 5 comments 4 replies
-
|
Does anyone answer these messages or respond? |
Beta Was this translation helpful? Give feedback.
-
|
@JustAddSoftware sure, don't put a symlink in your container volume that points to /var/spool/cron/crontabs/librenms. |
Beta Was this translation helpful? Give feedback.
-
|
Where is the symlink? It’s not in my compose file.
Sent from my iPhoneOn Nov 29, 2025, at 10:42 AM, Tony Murray ***@***.***> wrote:
@JustAddSoftware sure, don't put a symlink in your container volume that points to /var/spool/cron/crontabs/librenms.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
no, it's in your file system. the startup script chown everything in the librenms directory. If there is a symlink, it follows it. search /data inside the container or /share/Container/LibreNMS/librenms outside the container. |
Beta Was this translation helpful? Give feedback.
-
|
How can I edit the startup script?It’s in the Container. Why would the container package even have it? Where would it be to edit?Sent from my iPhoneOn Dec 1, 2025, at 8:28 PM, Tony Murray ***@***.***> wrote:
It looks like the startup scripts try to chown that file, which fails on your system for some reason. (maybe non-root?)
You could try to remove the chown from the start up script.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone,
I am trying to get librenms set up and running in Container Station on a QNAP NAS. I am running into an error when the container is starting up. I am getting this error when configuring the crontabs and it seems to be killing the entire process:
Shortly after this, all processes are stopped and then things start up again and repeat over and over.
Below is my YAML code from my Compose file. Because default file locations in QNAP are stuck in a spot where you can't access them, I am putting my volumes in a folder I have created called /share/Containers/LibreNMS - so all the volumes are mapped there.
What might be wrong?
Beta Was this translation helpful? Give feedback.
All reactions