Hey there (I'm new to unraid),

 

I've added the a container path /control-center pointing to my host path /boot/config/plugins/compose.manager/projects/control-center/.

 

However when using this path within container I am met with "Unable to read path on disk. Please check the path and try again.".

I've checked the Privileged checkbox in the container settings, but that hasn't fixed it.

I suspect this has something to do with permissions, so the question would be how can I give it the correct permissions.

Or am I doing something wrong?

What permissions are required?    Note that files on /boot are not allowed to have ‘execute’ permissions for security reasons.

It looks like you are trying to access compose files from the compose plugin in some other application. This is not recommended. You really should not mess with the files in the compose plugins project directory.

 

If you must access compose files from something else the compose plugin has an option, when creating stacks, to choose a directory in which to store the compose file, that allows you to place it on the array or in a pool rather than on the boot drive. This also separates the compose file itself from the files compose manager uses to manage the stack.

Edited December 26, 20241 yr by primeval_god

10 hours ago, itimpi said:

What permissions are required?    Note that files on /boot are not allowed to have ‘execute’ permissions for security reasons.

Read/Write I would assume, it's simply to sync my compose files with my Github repository.

6 hours ago, primeval_god said:

It looks like you are trying to access compose files from the compose plugin in some other application. This is not recommended. You really should not mess with the files in the compose plugins project directory.

 

If you must access compose files from something else the compose plugin has an option, when creating stacks, to choose a directory in which to store the compose file, that allows you to place it on the array or in a pool rather than on the boot drive. This also separates the compose file itself from the files compose manager uses to manage the stack.

It needs to be the compose files as this is the exact target, it's basically to sync my compose projects with Github.
I misread what you said, I understand now.
I'll override the directory and see if that works.

Edited December 26, 20241 yr by DespairServices
Misunderstanding

And some of the projects themselves aren't simple docker-compose.yml, there's actual code that needs to be compiled, hence why I use Github.
Hopefully this is possible, because I really wouldn't want to have to manually copy and paste everything through ssh every time I make a change.

I also do not wish to upgrade my docker account for this, considering I am already well acquainted with Github, and it's just for private repositories.