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
Docker Fails on RPi #66
Comments
I do not have RPi currently to test, but I am suspicious about RPi's docker-compose... Anyway - I will mark this as a bug. Can anybody reproduce this on RPi and confirm that bug exists? |
Strange, I just got mail notification from GitHub: |
Anyway - All Mainflux Docker images are built by the DockerHub automated build on x64 machines. For RPi packaging we must use ARM compiled images, and that probably means resin.io and Hypriot containers, somethingsimilar to this: https://github.com/hypriot/rpi-golang/blob/master/Dockerfile Moreover, Mainflux uses EMQ and for the moment I have no idea how will we port this piece of Erlang code to RPi... I guess it can be done, I've seen VerneMQ has been ported to Pine64 few days ago: https://syshell.net/2016/11/05/vernemq-install-it-on-pine64/ We have to see this with EMQ community... |
Probably best approach for the first iteration would be to run Mainflux on PC (on Vm for example) connect RPi to this machine in private LAN via ETH and then run Mosquitto on RPi and bridge it similar to this: emqx/emqx#718 I have not tried this set-up yet, but it should work... @mijicd how will this affect auth? If Mosquitto is bridged to EMQTTD it should be seen like one big cluster, and auth should work correctly. |
I managed to bring up mainflux on RPI 3 |
@gesaleh great, thanks. We are wondering about Docker also, please let us know if you have this one running. It will probably demand change in the Dockerfile (maybe to include Hypriot), and if yes, I'd gladly accept PR :) |
FYI, I've created https://github.com/mainflux/mainflux/blob/master/install_sources.sh to help installation from the sources. |
Closing this one. |
Signed-off-by: Manuel Imperiale <manuel.imperiale@gmail.com>
Signed-off-by: Drasko Draskovic <drasko.draskovic@gmail.com>
The text was updated successfully, but these errors were encountered: