At the beginning of this project, I had waayyyy too many tabs open. I hated reopening the same windows for weeks, so I put them here instead.
repos/npm packages
- Raspberry Pi and Crossbar.io IoT Starterkit Cookbook
- Node-gyp: Node.js native addon build tool
- resin-rpi-py-ADC
- pi-pins
- recommended by resin for raspi/docker GPIO use… don’t really want to go this route since I’m already using johnny-five/raspi-io
- node-i2c: native bindings for i2c-dev
- i2c-dev is holding up my app build; I don’t even use the i2c pins on the rpi; can I get rid of this module altogether?
- i2c-nodejs
- rpi-kernel: build a linux kernel for raspi
- hypriot/flash: flash SD card image of any kind
- docker hub: rpi-i2cdisplay
- dockerfile-node-gpio-express
- possibility if I can get the gate-counter to work without johnny-five
- nebrius/raspi-io
- the library that is currently giving me issues
- their gitter channel
- pi-gen: create raspbian images
- raspbian-live-build: raspi disk image builder
stack overflows/gists
- How do you install something that needs restart in a Dockerfile?
- Using Docker with nodejs with node-gyp dependencies
- Within a docker build, Modules dependant on node-gyp fail
- Running a docker container as a non-root user
- “Could not open moddep file …” when mounting using a loop
- could not open moddep file modules.dep.bin
- How do I configure modprobe to find my module?
- Streaming Video modprobe ERROR
- “could not insert i2c_dev” error with resinOS and Raspberry Pi 2
- specific johnny-five problem with resin library
- Disable i2c in Raspberry pi
- RaspberryPi.org forums: I2C not working
- nebrius/raspi: ERROR: could not insert ‘i2c_dev’
- Enable i2c on ubuntu mate raspberry pi 3
- Lsmod and modprobe not found
- Docker loading kernel modules
- GPIO access issues were also resolved for some users by giving docker container access to the kernel of the machine running it using the
--priveleged --cap-add=ALLflags
- GPIO access issues were also resolved for some users by giving docker container access to the kernel of the machine running it using the
- Access GPIO pins without root. No access to /dev/mem. Try running as root!
- nebrius/raspi-io: ENOENT: no such file or directory
- nebrius/raspi-io: Troubles when using hypriot images and docker (johnny-five)
blogs/docs
- nodejs.org: Dockerizing a Node.js web app
- nodejs/docker-node: Docker and Node.js Best Practices
- The easy way to set up Docker on Raspberry Pi
- How to debug and fix common docker issues
- Control GPIO with Docker Swarm
- Create a Docker container for raspberry pi to blink an LED
- uses python, so might not be very helpful, but builds from docker’s official
architectures-other-than-amd64instead of resin or hypriot
- uses python, so might not be very helpful, but builds from docker’s official
- Activate the i2c bus of Raspberry Pi 3 or Pi Zero W
- Configuring GPIO - adafruit
- Troubleshoot volume errors
- some googling revealed that the issue with the GPIO could be that the docker container can’t access the pins; this approach gives the container permission to mount a volume (
/dev/mem) to get to a device’s memory
- some googling revealed that the issue with the GPIO could be that the docker container can’t access the pins; this approach gives the container permission to mount a volume (
- docker run
- modprobe in a docker container