January 15, 20251 yr Community Expert 13 minutes ago, kjclark23 said: -v '/mnt':'/storage':'ro' Your mapping for /storage specifies ro Also, you shouldn't map anything to /mnt Looks like the default template for that container has /storage mapped to /mnt/user
January 15, 20251 yr Author I see this now. This is interesting. Can these settings get changed on their own? I did not change this and wonder why it didn't work, lol. Curious how it has been working for such a long time. But I changed the /storage to "rw" and fixed the /mnt to /mnt/user. I'm really not sure if the /mnt was always like that or if I had the default (which I usually keep). Just really not sure how this even happened.
January 15, 20251 yr Community Expert The default template also has /storage as ro, which I guess makes sense if this is supposed to be the source data. 26 minutes ago, kjclark23 said: Failed to save title 0 to file /storage/user/Media/Rip Here First/Rankin_Bass Holiday Favorites.mkv This path actually winds up being in /mnt/user anyway though, since it is /storage/user, so that mapping would probably work if it wasn't ro. But do you really want /storage to be rw?
January 15, 20251 yr Community Expert 5 minutes ago, kjclark23 said: But I changed the /storage to "rw" but do you really want the source data to be rw? 6 minutes ago, kjclark23 said: fixed the /mnt to /mnt/user That path specified in the error message /storage/user..., would map to /mnt/user/user, in other words, a user share actually named "user", which would be created as a new user share if it didn't already exist if you tried to write to it. And a user share by that name not recommended. Probably the actual path in the container you got to by browsing to it in the application though. Do you understand docker volume mapping?
January 15, 20251 yr Author Do I understand docker volume mapping? I can't really explain it myself, so no. I didn't think I would want the /storage to "rw", but changed it to see if the docker would then work. For the path, I have it mapped within MakeMKV GUI to send to just /storage (without /user). I guess I needed to change this in the settings too. I didn't originally have it this way, use to work for a long time. MakeMKV gave me a pop-up stating that the path doesn't exist, which I thought was odd. So I changed it in the GUI to get it working. Not sure if this has anything to do with updating to Unraid 7.
January 15, 20251 yr Author I went and changed the /storage back to "ro" and MakeMKV is back to stating it is in read only mode and I get an error. I'm finally seeing, thanks to your post, that MakeMKV is somehow defaulting to using the /storage for its output. Not sure how this automatically happened, but I changed it to /output which has "rw". Seems to be working now, really sorry to waste your time on this. I will always be learning with this stuff. Edited January 15, 20251 yr by kjclark23
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.