Unable to open database file.....

[qdm12]

Unable to open database file.....

[UntouchedWagons]

Still says unable to open database file {"node_id": 0} in logs

[Edit]

I changed the ownership of /docker/ddns-updater to 1000:1000 and it's sort of working now.

[Edit #2]

Yeah it's fine now, I added an A+ Dynamic DNS Record and it's fine now.

I had seen the instructions that the config file was to be owned by the user docker used, but I've never had to do that for any other docker container before so I was a bit confused.

[danmed]

I'm an idiot.

[qdm12]

Don't be harsh on you, it happens to all of us 😄

However, did the line 2019/04/29 15:36:32 Info: Node 0: Found 1 records to update came before the rest? That seems odd and should not happen 🤔

Also you might want to pull the last image as I fixed several things today. Thanks !

[danmed]

I may have incorrectly copied the output.. I had simply forgotten to set permissions on the data folder :)

…

On Mon, 29 Apr 2019, 16:43 Quentin McGaw, ***@***.***> wrote: Don't be harsh on you, it happens to all of us 😄 However, did the line 2019/04/29 15:36:32 Info: Node 0: Found 1 records to update came before the rest? That seems odd and should not happen 🤔 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA5S4WULK4ZCZXQYATXXSEDPS4JQ5ANCNFSM4HJENY6Q> .

[UntouchedWagons]

What did you do to fix this? I'm having the same issue and have no idea what the problem is. https://xkcd.com/979/

[qdm12]

Please post back the output from ls -l on the directory containing the database file to see permissions and ownership.

Merry Christmas 🎄 !

[UntouchedWagons]

$ls -l /docker/ddns-updater 
total 5
-rw-r--r-- 1 root root 295 Dec 25 02:09 config.json

[qdm12]

Yes it's owned by root that's why it doesn't work.

Run this to make it owned by user ID 1000 and group ID 1000:

chown 1000:1000 /docker/ddns-updater/config.json

[qdm12]

If you bind mount the directory, you have to change the ownership of the directory too, forgot to mention. In my case I only bind mount the config file.

Most containers out there use the root user by default, which is dangerous as anyone getting access to the container can almost do anything your host root user can do, see this for more information for example.

Sometimes root user is needed (i. e. run a VPN) but 90% of the time it's not.

The disadvantage is that you have to match the bind mounted files with the user running the container. Note that you can change the user running the container with --user=1001:1001 for example or --user="root".