Phill

Then don't upgrade. I don't mean that in any snippy or snarky sense. I mean it as honest advice. I haven't upgraded. I'm still on old menu. `git checkout old-menu`....

It probably means what it says (basically, your pwfile is in the wrong place or might have the wrong permissions). You didn't include any of the relevant files in your...

Hi - NodeRed and SQLite (as you've implemented it here) are separate **containers**. Focus on what a "container" means. It means that NodeRed can see it's own data but can't...

To me, that sounds like you are relying on a relative path inside the container and I don't think that's a good idea. We don't control how the base Node-Red...

No. You only need the `- ./volumes/nodered/data:/data`. Everything inside the "data" directory (files, folders, as deep as the folder structure goes) is all shared.

If you erase ./volumes or ./volumes/nodered then you will indeed lose your databases. But if you mean "will re-running the menu destroy databases?", the answer is no. They will be...

I don't know whether this will help as a reference. Fairly obviously, it's just the containers I run so you might need to ferret about in your own system to...

Try: ``` $ cd ~/IOTstack $ docker-compose stop prometheus $ docker-compose rm -f prometheus $ sudo rm -rf ./services/prometheus/config.yml $ cp ./.templates/prometheus/config.yml ./services/prometheus/ $ docker-compose up -d prometheus ``` The...

I don't think there's any way to "fix" this kind of problem. The real problem is that something happened on your RPi that deleted the config.yml file. If you don't...

I'm going to add some cross-references here in case they help with issues which have the same basic underlying cause (new menu not really supporting service definitions which have not...