This project has been migrated. Please find the maintained version at: https://github.com/SensorsIot/IOTstack
This project has been migrated. Please find the maintained version at: https://github.com/SensorsIot/IOTstack
To migrate your current IOTstack version, you can run:
$ cd ~/IOTstack
$ git remote set-url origin https://github.com/SensorsIot/IOTstack.git
$ git fetch origin master
$ git reset --hard origin/master
$ docker-compose down
$ ./menu.sh
$ docker-compose up -d
This will override any changes you've made locally on files git tracks.
If you have questions about migrating your current stack, or why the migration occured, please ask on the Discord: https://discord.gg/ZpKHnks
Any PRs created, or issues raised on this repo may not be answered.
IOTstack is a builder for docker-compose to easily make and maintain IoT stacks on the Raspberry Pi
The bulk of the README has moved to the Wiki. Please check it out here
Docker stack for getting started on IoT on the Raspberry Pi.
This Docker stack consists of:
- Node-RED
- Grafana
- InfluxDB
- Postgres
- Mosquitto mqtt
- Portainer
- Adminer
- openHAB
- Home Assistant (HASSIO)
- zigbee2mqtt
- Pi-Hole
- TasmoAdmin (parial wiki)
- Plex media server
- Telegraf (wiki coming soon)
- RTL_433
- EspruinoHub (testing)
- MotionEye
- MariaDB
- Plex
- Homebridge
In addition, there is a write-up and some scripts to get a dynamic DNS via duckdns and VPN up and running.
Firstly what is docker? The correct question is "what are containers?". Docker is just one of the utilities to run a container.
A Container can be thought of as ultra-minimal virtual machines, they are a collection of binaries that run in a sandbox environment. You download a preconfigured base image and create a new container. Only the differences between the base and your "VM" are stored. Containers don't have GUIs so generally the way you interact with them is via web services or you can launch into a terminal. One of the major advantages is that the image comes mostly preconfigured.
There are pro's and cons for using native installs vs containers. For me, one of the best parts of containers is that it doesn't "clutter" your device. If you don't need Postgres anymore then just stop and delete the container. It will be like the container was never there.
The container will fail if you try to run the docker and native vesions as the same time. It is best to install this on a fresh system.
For those looking for a script that installs native applications check out Peter Scargill's script
Raspberry Pi 3B and 4B Raspbian (Buster)
Docker will not run on a PiZero or A model 1 because of the CPU. It has not been tested on a Model 2. You can still use Peter Scargill's script
For those wanting to test out the script in a Virtual Machine before installing on their Pi there are some limitations. The script is designed to work with Debian based distributions. Not all the container have x86_64 images. For example Portainer does not and will give an error when you try and start the stack. Please see the pinned issue #29, there is more info there.
Please direct all feature requests to Discord
This repo was originally inspired by Andreas Spiess's video on using some of these tools. Some containers have been added to extend its functionality.
YouTube video: This is an alternative approach to the setup. Be sure to watch the video for the instructions. Just note that the network addresses are different, see the wiki under Docker Networks.
@peyanski (Kiril) made a YouTube video on getting started using the project, check it out here
1.On the lite image you will need to install git first
sudo apt-get install git2.Download the repository with:
git clone https://github.com/gcgarner/IOTstack.git ~/IOTstackDue to some script restraints, this project needs to be stored in ~/IOTstack
3.To enter the directory run:
cd ~/IOTstackI've added a menu to make things easier. It is good to familiarise yourself with the installation process. The menu can be used to install docker and build the docker-compose.yml file necessary for starting the stack. It also runs a few common commands. I do recommend you start to learn the docker and docker-compose commands if you plan on using docker in the long run. I've added several helper scripts, have a look inside.
Navigate to the project folder and run ./menu.sh
Select the first option and follow the prompts
docker-compose uses the docker-compose.yml file to configure all the services. Run through the menu to select the options you want to install.
This menu executes shell scripts in the root of the project. It is not necessary to run them from the menu. Open up the shell script files to see what is inside and what they do.
Some helpful commands have been added like disabling swap.
From this point on make sure you are executing the commands from inside the project folder. Docker-compose commands need to be run from the folder where the docker-compose.yml is located. If you want to move the folder make sure you move the whole project folder.
to start the stack navigate to the project folder containing the docker-compose.yml file
To start the stack run:
docker-compose up -d or ./scripts/start.sh
To stop:
docker-compose stop
The first time you run 'start' the stack docker will download all the images for the web. Depending on how many containers you selected and your internet speed this can take a long while.
The docker-compose down command stops the containers then deletes them.
Docker allows you to map folders inside your containers to folders on the disk. This is done with the "volume" key. There are two types of volumes. Modification to the container are reflected in the volume.
Feel free to add your comments on features or images that you think should be added.
If you use some of the tools in the project please consider donating or contributing on their projects. It doesn't have to be monetary, reporting bugs and PRs help improve the projects for everyone.
@mrmx, @oscrx, @brianimmel, @Slyke, @AugustasV, @Paulf007, @affankingkhan, @877dev, @Paraphraser, @stfnhmplr, @peyanski, @cmskedgell