AUREL – Worker Node

Hostname: AUREL
IPv4 Address: 192.168.1.123 (STATIC)
IPv6 Address: Any/Unused (Dynamic)
Assigned IPv4 DNS: 192.168.1.125 (ENLIL)
Assigned IPv6 DNS: 2a00:23c7:593:6501:ba27:ebff:fe0f:e3f2 (ENLIL)
Architecture: ARMv7 (Raspberry Pi 3 B+)

Purpose

AUREL acts as a dedicated worker within the home-lab CI/CD infrastructure. It is responsible for executing all heavy build and test workloads, keeping orchestration and scheduling separate using docker context or manually setup SSH commands.

Executes Docker builds and test jobs.
Runs ARM-native workloads.
Acts as a remote Docker host.
Receives jobs indirectly from LORIC via SSH or Docker context over SSH.

System Information

Kernel / OS

Kernel: 6.12.62+rpt-rpi-v8
Build: #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1 (2025-12-18)
Architecture: aarch64
Distro: Debian (Raspberry Pi variant)

SSH Stack

OpenSSH: OpenSSH_10.0p2 Debian-7
OpenSSL: 3.5.4 (30 Sep 2025)

Docker

Docker Engine: 26.1.5+dfsg1
Build: a72d7cd

Services & Packages Running

Docker Engine – container builds and test execution.
OpenSSH Server – secure remote job execution.
Git – source code checkout.
Build tools – build-essential for native compilation.
System utilities – curl, jq, ca-certificates.

Setup Steps

AUREL was setup using the following steps and instructions:

1. Setup Network Manager CLI for AUREL

We will use the following command to set a static IPv4 on our device and ensure that IPv4 and IPv6 dns are set correctly.

At the moment there is no requirement for this device to have a static IPv6 yet.
DNS IPs point towards ENLIL.

auzlex@AUREL:~ $ sudo nmcli connection modify "target connection" \
    ipv4.addresses 192.168.1.123/24 \
    ipv4.gateway 192.168.1.254 \
    ipv4.dns 192.168.1.125 \
    ipv4.ignore-auto-dns yes \
    ipv4.method manual \
    ipv6.dns 2a00:23c7:593:6501:ba27:ebff:fe0f:e3f2 \
    ipv6.ignore-auto-dns yes \
    ipv6.method auto

We then apply changes by rebooting

auzlex@AUREL:~ $ sudo reboot

verify

auzlex@AUREL:~ $ nmcli

2. Install Docker

auzlex@AUREL:~ $ sudo apt update && sudo apt install -y docker.io docker-compose && sudo systemctl enable docker --now

Docker is used to run any containerized jobs dispatched from LORIC.

3. Setup SSH For Isolated CI user

We will create a user ci which will be used for build related workloads and for isolation. This user will recieve remote jobs or commands via SSH from LORIC.

Create user with password and set shell (choose a strong password, record it for SSH key setup):
```
 sudo useradd -m -s /bin/bash ci
 sudo passwd ci
```
Add user to Docker group:
```
 sudo usermod -aG docker ci
```
Verify membership:
```
 getent group docker | grep ci
```

Enable SSH access:

 sudo systemctl enable ssh && sudo systemctl start ssh

Generate SSH key for passwordless login from LORIC:
```
 sudo -u ci ssh-keygen -t ed25519 -C "ci@AUREL" -f /home/ci/.ssh/id_ed25519
```
- Copy the public key to LORIC runner or other orchestrator nodes for secure job execution.
Test SSH login (password initially, then test key-based auth):
```
 ssh ci@192.168.1.123
```
Verify home directory ownership:
```
 ls -ld /home/ci
```

Notes

Accessible on the local network via SSH.
Does not expose public services.
Docker is the main execution environment for all workloads, ensure it remains updated.
All jobs are executed under ci to maintain isolation.
For troubleshooting, check logs in /var/log/syslog or use journalctl -u ssh for SSH issues.
Any workspace directories must remain owned by ci for correct job permissions.