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

[BUG] UNRAID APP - Failed to create config directory. #3029

Closed
2 tasks done
mscrnt opened this issue Sep 11, 2024 · 1 comment
Closed
2 tasks done

[BUG] UNRAID APP - Failed to create config directory. #3029

mscrnt opened this issue Sep 11, 2024 · 1 comment
Labels
BUG Something isn't working

Comments

@mscrnt
Copy link

mscrnt commented Sep 11, 2024

Is this a bug in companion itself or a module?

  • I believe this to be a bug in companion

Is there an existing issue for this?

  • I have searched the existing issues

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

  1. Install Bitfocus Companion from the community app store.
  2. Make sure all fields are filled out correctly and click done.
  3. Wait for the app to download and start the container automatically.
  4. Notice the app doesn't start.
  5. View logs and see error message.

Expected Behavior

App should start without any additional steps.

Environment (please complete the following information)

- OS: UNRAID
- Browser: Chrome
- Companion Version: Latest (3.4?)

Additional context

When running the container in interactive mode, I see the companion folder is created and seems to have the correct usergroup.

@mscrnt mscrnt added the BUG Something isn't working label Sep 11, 2024
@Julusian
Copy link
Member

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?

@Julusian Julusian closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants