The Raspberry Pi and most of the other similar ARM processors based devices are just great and fun: it exists thousand of micro projects on the web designed to run on these single board computers.
However, most of these projects are proposing us to burn a sd card. But we don't have 20 SD-cards, and we don't want to have to switch between SD Cards. We just want to have and one SD card, that will contain some of these fun projects, and a possibility to turn on and off these projects (because we all know that our small computer can't start them all at the same time).
That's one of the reason of the birth of the 'Brother in Arms' project.
But more generally, the 'Brother in Arms' projects' goals are:
- be able to bring on a single SD-Card some of the great open-source projects we can find all over the web
- provide a simple way to install them
- provide binaries that user can trust
And how will we do this ? Thanks to Docker !
Currently, the work is in progress, and we are far for where we want to go. But we started anyway to publish some first alpha project, just in case other people wants to joint ;) In that case, don't hesitate to contact the Brother In Arms's project team via project.biarms@gmail.com.
If you are interested to test where we are, have a look to https://github.com/biarms/bootstrap.
- Setup a pi with wifi and access point (first wlan -> connect the network, second wlan: provide an access point)
- Portainer, to see what is running
- Shairport-sync to play music on my legacy hifi system with my iPhone thanks to AirPlay
- A DynDNS service to expose the box on Internet (if needed)
- An email service, to be able to send email
- The admin env MUST be able to turn on and off the 'application' listed below
- The admin env COULD be able to configure part of the system
Setup an 'application layer' that could provide some easy to install ARM-based docker stack (that's the goal of this repo):
- Deploy a WordPress env to host a Blog
- Deploy Ghost (because its is a good alternative to Wordpress)
- Deploy NextCloudPi
- New application add-on MUST be based on docker
- New application add-on SHOULD only use 'trusted docker' container (only official images, otherwise, we rebuild). We have infinite thanks for hypriot and resin team's, but as docker is now working out-of-the-box on arm-ubuntu, raspbian, etc, we prefere to use the 'main stream'.
- No more docker compose, but docker stack (to be ready to deploy in a SWARM or K8S cluster. The 'single device' mode will be based on a 'docker swarm with only one node'. (MUST)
- Use 'secret_file' instead of env variable or secret variable to store secrets (SHOULD)
- When possible, Dockerfile should be based on 'alpine:3.11.6' (alternative: every biarms rebuild image SHOULD inherit from the same base image, to reduce disk usage)
- Build Mysql and WordPress image with the 'arm' architecture flag on (needed for swarm), supporting '_file' extension (ie: MYSQL_ROOT_PASSWORD_FILE)
- Deploy WordPress
- Focus on RPI1 + Odroid XU4 only (OrangePi + RPI2/3 should be OK, but were not tested)
- Deprecated (at least temporary) RPI1 support, because of 'docker pull' bug (version 19.03.8) for 'arm32v6' device with 'CPU architecture' set to 7. See biarms/mysql#4 -> moby/moby#41017 -> moby/moby#34875
- Add Gogs and Portainer stacks
- Add Gitea stacks, but only for arm64v8 and arm64 platform (Gogs should be used for older/smaller devices)
- Add amd64/x86_64 support
- Focus on arm32v7('Odroid XU4') and arm64v8('RPI3') only (OrangePi should be OK, but were not tested)
- Create an Wifi access point docker container (with hardcoded ip)
- Create a stack to start Portainer.io
- Create a stack to install Nextcloud
- Create an UI application to help people to install these tools
- Create a bootable image embbeding this UI application (base on ubuntu-20.04-aarch64 ?) that should run on RPI3 and RPI4
- Also create a bootable image for other arm devices
- Create a git repo per stack
- Add more funny arm based and open-source stacks (ie: shairport-sync)