ejg3855 Posted April 3 Share Posted April 3 This is likely a simple over sight on my part but I am trying to add a path to ./media/..... when I am using the Orca Slicer docker build. I have files on the unraid array I want to be able to access and work with in that environment. I don't know if I am working with Orcaslicer wrong of if this is a setting is something to do with the backend of my unraid docker confg. Quote Link to comment
itimpi Posted April 4 Share Posted April 4 Not familiar with that container, but you have given no container path for the 3D Prints mapping to make them visible inside the container - is that intentional? Quote Link to comment
ejg3855 Posted April 4 Author Share Posted April 4 I thoughts thats what I did when I added the path I do see it says container path and that could be the source of the error. what would I need it to be configure as? Quote Link to comment
itimpi Posted April 5 Share Posted April 5 17 hours ago, ejg3855 said: I thoughts thats what I did when I added the path I do see it says container path and that could be the source of the error. what would I need it to be configure as? Whatever the container is looking for it to appear as inside the container. Basically the container path is where the container ‘thinks’ the file or folder is located and the other part is where it is really located at the Unraid level. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.