Updated 3.1 Raspberry Pi setup using IOTStack (markdown)
suggestion from paraphaser - The screen shot after You should see the following docker containers will need an update because Mosquitto is now a base and local image.)
info on mosquitto passwords explained - please edit or delete as you think is best
And another one: exit menu.sh and run sudo docker ps. If you need sudo to run docker then it kinda implies the underlying installation was incorrect. See https://gist.github.com/Paraphraser/d119ae81f9e60a94e1209986d8c9e42f which goes through how to uninstall things and reinstall them properly. In my opinion, the way IOTstack installs its dependencies needs an overhaul. If you hunt through the various scripts there are inconsistencies all over the place, to the point where you get different results depending on how you attack the problem. The way I build my Pis is documented at https://github.com/Paraphraser/PiBuilder - I do not go near any menu or other IOTstack-supplied installation process because of these inconsistencies. I like my builds to be predictable. :nerd: Gist
sudo not recommended - see previous note
sudo not recommended (Paraphraser — Today at 9:11 PM From that URL Run IOTStack: sudo ./menu.sh is a perfect example of sudo overuse. The menu invokes sudo when needed. If you try to run the menu and something happens which suggests sudo might be needed when starting the menu, it actually means something else is wrong. I tried to "solve" this problem by sticking a check at the start of the menu which said "don't use sudo". That check is still in the menu on old-menu branch but it somehow disappeared when the new menu (master branch) got created. It's a shame because the menu.sh script does assume that $HOME is /home/pi. That assumption is violated when you start the menu with sudo and then all hell breaks loose. I'll keep reading to see if I spot anything else.)
Created 3.1 Raspberry Pi setup using IOTStack (markdown)