-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continue to get Connection Refused Error at end of Set-up #6
Comments
It looks like your docker containers aren't running. Can you show the output of:
You should see a few images listed. If not, part of the setup didn't work. Try this, too, and send the output: cd tempiture # or whatever your tempiture folder is named
docker-compose -f ./docker/docker-compose.yml -p tempiture up |
I see now that you're on buster. This has only been tested on jessie. It doesn't look like there are docker-hypriot packages for buster (yet or at all). But it does seem that docker is available from the repo for buster. Can you try installing docker and docker-compose from the repo? sudo apt-get update
sudo apt-get install docker.io docker-compose If that doesn't work, take a look at this thread and see if some of the alternate solutions work. Supposedly this one-line works Also, it looks like npm isn't installed. Check the output from setup.sh to look for errors about the npm install. (Or you can just install it manually) Once you have docker and npm installed, you can comment out lines 8, 22-27 in the setup.sh and if all goes well, be up and running. |
Thanks for your help. After fighting with docker for a while and getting nowhere, I decided to go my own way. I started over and went with InfluxDB and Grafana. I will probably comeback and retry what you have here with a fresh Stretch install and see if that works. |
On repeated attempts on a Raspberry Pi3B running Buster, complete the set-up but with the error curl: (7) Failed to connect to tempiture.local port 3000: Connection refused just before the end.
The text was updated successfully, but these errors were encountered: