RAKPiOS Tools

Raspberry Pi `raspi-config` Tool

RAKPiOS is pre-installed with the official command-line utility tool for the Raspberry Pi OS, called raspi-config. This tool is used to configure various Raspberry Pi settings and options, such as system settings, interface settings, performance settings, and more.

Zoom Level:

Figure 1: raspi-config tool

NOTE

raspi-config uses dhcpcd to manage network connections, while RAKPiOS uses NetworkManager to manage WiFi and 4G connections. If both of these tools are used to manage the same network interface, they may cause issues with IP address assignment and network connectivity.
To prevent these conflicts, dhcpcd is disabled by default in RAKPiOS, ensuring that NetworkManager is the sole tool used to manage network connections. This approach ensures that RAKPiOS users have stable and reliable network connectivity.
Avoid managing your network with raspi-config and use rakpios-cli tool instead.

OLED Script

RAKPiOS includes a script that displays information messages on an OLED screen if one is available (as in the WisGate Connect). This script is designed to work with monochrome OLED screens based on SSD1306 drivers, and the source code is available on GitHub.

The OLED script generates multiple pages that display critical system information such as the system name and version ID, network status, system hardware status, running containers, and power failure notifications. By displaying this information on the OLED screen, you can quickly and easily monitor the status of their system and take appropriate action.

The OLED script is designed to be easy to use and highly customizable. You can modify the script to display additional information or customize the layout of the display pages to meet their specific needs.

If you need to disable the OLED script, edit the /etc/rc.local file and comment out the line that calls the script:

# Display basic info on oled screen
#/bin/oled &

exit 0

Miromico Miro EdgeCard mioty® Management

Refer to the Miromico Miro EdgeCard mioty® Management page.

Deploy on Boot Folder

RAKPiOS is built on the official Raspberry Pi OS image, with all changes made defined in the stage2-rak repo. This stage contains an on boot folder that allows users to create an image that can deploy Docker services on the first boot. The scripts required to implement this feature are included in the .04-pre-install-containers folder.

By default, this stage is hidden, and users can use a command such as ls -a to view it. The stage is optional and serves the purpose of having Docker containers installed by default on boot and running a set of commands on the device's first boot to install Docker-related services or tools.

Remove the dot at the beginning of the directory to activate this stage when building a new image. This will download the compressed images for the UDP packet forwarder, Basic station packet forwarder, Portainer, and The Things Stack, then save them to /usr/local/etc/images (see stage2-rak/.04-pre-install-containers/00-run.sh).
To start with customized services during the first boot, a simple script called runonce is created (check stage2-rak/.04-pre-install-containers/files/runonce). This script can be used to start the customized services defined in the directory stage2-rak/.04-pre-install-containers/files/run-once-services.

Some example scripts are also provided:

To load the compressed image for Portainer and start the Portainer service during the first boot:
- stage2-rak/.04-pre-install-containers/files/run-once-services/portainer.sh.sample
To load the required images defined in the .YML file:
- stage2-rak/.04-pre-install-containers/files/docker-compose-file
To start the services:
- stage2-rak/.04-pre-install-containers/files/run-once-services/docker-compose.sh.sample

Once a script stored in stage2-rak/.04-pre-install-containers/files/run-once-services is completed, it will be moved to the host's directory /etc/local/runonce.d/ran, with the date and time appended to its name. There will also be an entry in your syslog.
To add customized compressed Docker images to the customized RAKPiOS image, use the docker save command to create the compressed images first. For example, docker save -o container-tar-portainer.tar portainer/portainer-ce:2.16.0 will save the image portainer/portainer-ce:2.16.0 as a compressed file called container-tar-portainer.tar.
Move the compressed images to the RAKPiOS build directory. You can also download the images provided - refer to stage2-rak/.04-pre-install-containers/00-run.sh for example.
Use docker load to load the compressed images. Check stage2-rak/.04-pre-install-containers/files/run-once-services/portainer.sh.sample.