You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This sounds like unraid is doing something wrong with the config directory to me.
We are not involved in how this is setup in unraid, so I am going to close this.
It looks to me like the issue could be that it is setting up a config directory at /root/companion, instead of the correct path of /companion. https://github.com/Marraz/unraid-templates/blob/main/Companion/Companion.xml#L42-L52
Or maybe its because we no longer run companion as the root user and run it as node, maybe unraid isn't setting permissions in a way that works with that?
Is this a bug in companion itself or a module?
Is there an existing issue for this?
Describe the bug
The container fails when I try to start the unraid app. I see this in the logs.
Failed to create config directory. Do you have the correct permissions?
2024-09-10T22:13:27.769Z info Log/Controller Application starting
Steps To Reproduce
Bitfocus Companion
from the community app store.Expected Behavior
App should start without any additional steps.
Environment (please complete the following information)
Additional context
When running the container in interactive mode, I see the companion folder is created and seems to have the correct usergroup.
The text was updated successfully, but these errors were encountered: