Bitbass Posted May 13, 2023 Share Posted May 13, 2023 I've searched and haven't found an answer to this, so I'm probably asking the wrong question. However, I have a container I just added that has a config.json file in it that I need to edit. The json is owned by root and is not writeable from the container's cli. I'm unable to chmod to make it writeable. I'm also unable to map the path. Every time I try I get a failure to start because it can't find an app.js file or something similar. I'm sure this is just my lack of familiarity with the inner workings of Docker, so please be gentle. Quote Link to comment
Squid Posted May 13, 2023 Share Posted May 13, 2023 Use sudo to escallate the command? Quote Link to comment
Bitbass Posted May 13, 2023 Author Share Posted May 13, 2023 sudo not available inside the container. Quote Link to comment
Kilrah Posted May 13, 2023 Share Posted May 13, 2023 If that file is meaningful it should be mapped to appdata, so edit it from the unraid side. Quote Link to comment
Bitbass Posted May 13, 2023 Author Share Posted May 13, 2023 It's not mapped to appdata by default and if I add the path myself it fails with the error and won't start. It's possible I'm doing it wrong. Quote Link to comment
Kilrah Posted May 13, 2023 Share Posted May 13, 2023 To map a single file you'd want to copy the file from the container / create an identical one in appdata first, then map that - if it doesn't already exist it won't work Quote Link to comment
Bitbass Posted May 14, 2023 Author Share Posted May 14, 2023 Ah! Didn't know that. I'll give it a try. Quote Link to comment
Bitbass Posted May 14, 2023 Author Share Posted May 14, 2023 Ok, I think I understand now that I have to create the entire folder structure in the appdata folder or else it thinks it's missing. I can't find a way to make the single json editable, without recreating that entire structure, and I'm not sure what the best way is to recreate that in appdata. Quote Link to comment
Kilrah Posted May 14, 2023 Share Posted May 14, 2023 File to file mapping should work. How are you entering it? Quote Link to comment
Bitbass Posted May 21, 2023 Author Share Posted May 21, 2023 This one boots but doesn't link up the config file: This one also boots but doesn't link up the config file: Same for this one: I'm not sure what I was doing earlier that was causing it to not boot but it seems to be starting every time now. However, I haven't found the magic combo that allows me to edit the file. Placeholder file in appdata or not, the container file never changes. Quote Link to comment
Kilrah Posted May 21, 2023 Share Posted May 21, 2023 (edited) All of these mappings are folder to folder, if you want to overlay a single file in the container then you want the full path including filename on both sides. Edited May 21, 2023 by Kilrah Quote Link to comment
Bitbass Posted May 21, 2023 Author Share Posted May 21, 2023 When I do this it creates the config.json as a folder in appdata, instead of a file. Quote Link to comment
Bitbass Posted May 21, 2023 Author Share Posted May 21, 2023 If I put the file in the appdata location before mapping it using this: I don't see any change in the docker console when doing a cat on the file. It doesn't pick up the changed file in appdata. Just overrides it with the container version. Quote Link to comment
Solution Bitbass Posted May 28, 2023 Author Solution Share Posted May 28, 2023 (edited) I never figured out how to edit the defaults, but it appears this particular app does not allow for modifying the defaults anyway. You have to set the changes with URL switches. In my case, it's an image rendering size: &kiosk&height=1080&width=1920 As long as you specify this it allows you to override the defaults in the config file. Edited May 28, 2023 by Bitbass 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.