You can see which ports the system sees and which BrewPi thinks are compatible if you run: python autoSerial.py.
My guess is that you should try another USB cable. The USB connector on the Photon is picky. The pi probably doesn’t see the spark at all.
I switched cables and it now works after trying a third, but shortly after it showed the script as “running” it stoped again. Is there any way to fix this? TheUSB connection is so spotty that this is basically un-useable.
Maybe the USB connector on the Photon is damaged. They are fragile and a yank on the cable can cause it to become too loose.
If the internal part of the USB connector is damaged, only replacing the entire Photon is a good fix. If the outer shell got too loose to hold the cable in place properly, slightly bending it back py pushing down on the top can work.
Hello,
I few months ago I was having issues with a fresh install and I was pointed to the new docker based install. I downloaded Hypriot image 1.5 and flashed this to an 8GB and 32GB sd card, followed the instructions and everything went without a hitch. This was with 2 rpi3s.
I’m now trying to create a clean install for a test machine in my office and am using an old rpi box (gen 1?).
I took the exact same docker image which I have on a local drive and started up the box. The image installs fine and I’m able to ssh to the box. However, now when I try to execute the command docker pull brewpi/brewpi-raspbian and get an error message about the docker service not running and permission denied. See below.
My question is, why would the same image work twice and then fail? Would there be a incompatiability between certain libraries needed for the older pi box? If there were some incompatibilities I would expect larger issues just getting it up and running. There were no reported issues during start up.
Warning: failed to get default registry endpoint from daemon (Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.33/info: dial unix /var/run/docker.sock: connect: permission denied). Using system default: https://index.docker.io/v1/
I was setting up the old school raspberry PI and arduino set up and I got a bunch of errors trying to run the automated version of the install script.
Does this no longer work?
I use them with my glycol set up and run different temps on different fermenters.
Thanks
I wanted to drop a thank you to this group and the team at BrewPi! My old repurposed laptop running my Ubuntu software acting as web server finally took a dive on me. Fortunately it didn’t impact the brew already underway as the script was already loaded on the BrewPi. Anyway I had to build another machine up.
This time as I had newer hardware to build on, I did an Ubuntu 18.04 install. In reading online through the BrewPi wiki, I decided to install via using the Docker. Following those instructions, I needed an older Ubuntu, but chose to install VirtualBox instead to run Ubuntu 16.04.
Long story short, other than a couple of user rights issues between VirtualBox and my main OS, and enabling USB on the VirtualBox (which are challenges of my own doing because I chose to use VirtualBox), all instructions regarding Docker and BrewPi installation worked exactly as they should, and I got my BrewPi software up and running again pretty quickly. This went much faster than the first time I installed the software (pre-Docker days). Installing via the Docker was great, and I wanted to pass along great job!
My first brew since the rebuild is in the fermenter now!
Thanks! I’m running Ubuntu 18.04 too. Docker has no official release for it yet (expected to land later this month), but you can install the docker.io package instead, which will use the 16.04 release until the new one is officially out.
The current version of Raspbian Stretch with Desktop (available for download at https://www.raspberrypi.org/downloads/raspbian/, kernel version 4.14 and dated 2018-11-13) has a corrupted dockerd daemon/binary when running on certain ARM-based processors, including many Raspberry Pi units like mine. The fix is not in yet, but a workaround is documented at https://github.com/moby/moby/issues/38175. Prior to applying the fix I could not get the docker daemon to start. After applying the fix the daemon runs as expected.
Note that the same problematic binary will get installed on your Pi if you apply “sudo apt update” and “sudo apt dist-upgrade” over a working docker/portainer.
Hello, I struggle to have Portqiner properly installed on my raspberry pi 3. I have the following error message
“docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/create?name=portainer: dial unix /var/run/docker.sock: connect: permission denied.”
Does anybody has a solution for that?
Did you add the pi user to the docker group?
I launched the command “sudo usermod -aG docker pi”, is there anything else to do?
Maybe a reboot after that:)
