| Property | Value |
|---|---|
| Site | Home |
| Hypervisor host | VE-IO-01 |
| Role | Home GitLab CI Docker host. Runs the gitlab-runner (registered as runner ID 6, name VM-SL-41, executor docker, privileged) against https://git.blackreset.com, plus the portainer_agent (port 9001/tcp) connected into the Portainer EE on VM-SL-12. No public ingress — LAN-only. Idle workload (load avg 0.01) most of the time, spikes during CI runs. |
| OS | Debian 12 bookworm (running kernel 6.1.0-17, newer 6.1.0-44 staged — needs reboot, P-07) |
| Primary IP | 10.100.100.241 |
| SSH alias | vm-sl-41 |
| vCPU | 16 (AMD Ryzen 9 9900X 12-Core, KVM passthrough) |
| Memory | 5.9 GiB usable (Proxmox spec lists 16 GiB — mismatch P-08) |
| Storage | 200 GiB on local-zfs (4.8 GiB used post-cleanup) |
| Backup | PBS VM-image-level via VE-IO-01. Critical persistent state: /opt/gitlab-runner/config/config.toml (runner ID 6 token, cannot be regenerated without re-registering on git.blackreset.com) and the gitlab-runner anonymous volume 6d789f21… (/etc/gitlab-runner). CI cache volumes (the 34 orphan runner-*-cache-*) are not state — they will be regenerated on the next pipeline run. |
ens18 on bridge Server (VLAN 1000, MAC 00:0c:29:57:51:97), DHCP-assigned 10.100.100.241/24bridge, host, none — the solar-autoreset_default compose stack was removed during cleanup/etc/docker/daemon.json — log-rotation policy missing (P-02, preventive against the VM-SL-40 disk-full failure mode).| Property | Value |
|---|---|
| SSH user | alexander |
| SSH key (local) | E:/Workspace/Repositories/Clean Up/.secrets/ssh/blackreset_admin_ed25519 |
| Listening ports (notable) | 22 (SSH), 9001 (portainer_agent — only consumed by Portainer EE on VM-SL-12 over LAN) |
| Notes | LAN-only access; no inbound NAT forwards from RZ. Sudo passwordless via /etc/sudoers.d/alexander since 2026-04-29 onboarding. |
runner-*-cache-* Docker volumes from expired runner tokens / stale project IDs (≈ 837 MB) — listed in the protocol for per-volume confirmation before removal (P-03).unattended-upgrades not installed — outlier compared to SL-21 / SL-12 / SL-40 (P-05)./opt/docker/home-assistant (~911 MB, including a 949 MB home-assistant_v2.db) — RESOLVED 2026-04-29: user confirmed this was an early in-Docker HA experiment, abandoned in favour of the dedicated VM-SL-43 (HA OS, best practice). Original tree removed. A short-lived archive at /opt/archive/home-assistant-pre-sl43-2026-04-29.tar.gz was also deleted (user confirmation 2026-04-29) once it was clear PBS image backup retains the pre-removal state. /opt/docker and /opt/archive directories both removed; net disk reclaimed ~1.3 GB.privileged = true and bind-mounts /var/run/docker.sock — any CI job can root the host. Documented trade-off, P-09 to add it to the service wiki page.MaxUploadedArchiveSize = 0 (unbounded) — the upstream cause of the I-03 orphan-volume buildup.6.1.0-44 (6.1.164-1) is on disk but the system runs 6.1.0-17 (6.1.69-1). Reboot needed for security patches (P-07).solar-autoreset_default (image reg.git.blackreset.com:443/alexanderkorff/solar-autoreset:master) was removed during cleanup; no compose file on disk. Re-deploy from the GitLab repo if needed (P-10).GitLab-Runner ID 6 läuft hier weiter. Tag-Schema (per state_websites_migration_2026-05-01): home, stage, docker, vm-sl-41, legacy.
Neue Runner auf RZ:
vm-rz-app-prod-01 (Tags: rz, prod, docker, vm-rz-app-prod-01, heavy)vm-rz-app-stage-01 (Tags: rz, stage, docker, vm-rz-app-stage-01, builder)