API Key Changes on Reset

[smurfgun]

Do you know why there are 3 sets? I don't mean the double instance causing the problem... But I mean how there is one in volumes directory (which seems to be the one in use), one in overlay2/merged and one in overlay2/diff?

Lastly, is the docker directory expected? You mentioned it should be in /opt/alarmdecoder_webapp but it's actually in /var/lib/docker/......

Thanks!!!!

Ray

[kevin]

Would have to do a little research on docker volumes to understand that - will take some time.

But if you attach to the docker container, you will see it is indeed at /opt/alarmdecoder-webapp according to docker - but the local filesystem where the overlay filesystem for docker happens you will see it as you see it

So to get the real skinny, you have to attach to your docker container and see what's going on there - are there multiple copies in the docker container? Or just 2 keys in the one instance of the database?

Docker volumes are incremental so it could show up multiple times from the base OS but in the docker container itself, I'd be surprised if you had access to more than one of them. Likely just a duplicate key entry in that singular database in the docker container.

[smurfgun]

Ok... Thanks Kevin. The exercise is probably not required... If I have more problems with the double instance, I'd probably just nuke the SD card and start all over... It's a fairly quick process.

For now, it's fine... I used cmdline sqlite3 to modify the key and make sure it's the same on both. It can now come up as either instance on a reset and it should work fine...