struggling with creating the config.json in the right place #805
-
I'm trying to follow the steps in the guide. I'm running portainer on a raspberry pi. From the pi's user interface I ran the suggested commands and I created a directory here: /home/myname/updater/data/config.json I ran the commands to grant access but i'm not sure how to confirm they worked. I suspect I created the file in the wrong place. I'm not sure how to confirm the container is pointing to the directory that I created. I'm using the docker compose example provided, with the only modification being:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
I think maybe i pointed it to the file I created because now the log says
But i don't think it is working yet. My config.json file looks like this {
"settings": [
{
"provider": "porkbun",
"domain": "myname.homes",
"api_key": "abc",
"secret_api_key": "xyz",
"ip_version": "ipv4",
"ipv6_suffix": ""
}
]
} |
Beta Was this translation helpful? Give feedback.
-
In my experience, I had to populate the config.json file located in /updater/data/config/ which is one folder level deeper than where I initially expected. That may solve your problem. |
Beta Was this translation helpful? Give feedback.
-
If your file is at |
Beta Was this translation helpful? Give feedback.
If your file is at
/home/myname/updater/data/config.json
, you have to bind mount/home/myname/updater/data:/updater/data
and NOT/home/myname:/updater/data
. Right now ddns-updater created an empty json config.json file in /home/myname I would guess.