Add Portainer BE doc; update backup coverage for CT 109

- New services/portainer.md: BE license key, agent inventory, backup
  setup (Garage S3 + JottaCloud offsite), OIDC pending steps
- backrest.md: add CT 109 Portainer to coverage map, remove stale
  services/arcane path from plan, note Arcane decommission

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-05-26 17:12:36 +02:00
parent 07b21a7e2e
commit f65ceef90a
2 changed files with 133 additions and 2 deletions
+5 -2
View File
@@ -39,11 +39,12 @@
services/vaultwarden services/n8n services/memos services/vaultwarden services/n8n services/memos
services/karakeep services/traccar services/gitea services/karakeep services/traccar services/gitea
services/coder services/nextcloud services/pocketid services/coder services/nextcloud services/pocketid
services/arcane services/arr-stack services/gluetun services/arr-stack services/gluetun
backup/home-assistant backup/immich backup/nextcloud backup/home-assistant backup/immich backup/nextcloud
``` ```
`services/shared-db` was removed when CT 113 came online — postgres is now WAL-G → Garage S3 → JottaCloud. `services/shared-db` was removed when CT 113 came online — postgres is now WAL-G → Garage S3 → JottaCloud.
`services/arcane` removed 2026-05-26 — Arcane decommissioned, replaced by Portainer.
> **JottaCloud web UI tip**: rclone writes to the **Archive** section. The default landing page shows only Sync + Backup. Browse to `https://www.jottacloud.com/web/archive` to see the restic repos. > **JottaCloud web UI tip**: rclone writes to the **Archive** section. The default landing page shows only Sync + Backup. Browse to `https://www.jottacloud.com/web/archive` to see the restic repos.
@@ -82,6 +83,7 @@ Garage → JottaCloud offsite sync runs daily 02:30 on CT 103 via `/usr/local/sb
| CT 105 Nextcloud AIO volumes | AIO Borg → `/mnt/pve/unas/backup/nextcloud/` → Backrest | ✓ | | CT 105 Nextcloud AIO volumes | AIO Borg → `/mnt/pve/unas/backup/nextcloud/` → Backrest | ✓ |
| CT 108 Zoraxy | Phase 3 git push → `fkrebs/zoraxy-conf` | ✗ not deployed | | CT 108 Zoraxy | Phase 3 git push → `fkrebs/zoraxy-conf` | ✗ not deployed |
| CT 110 Pocket-ID | `services/pocketid` | ✓ | | CT 110 Pocket-ID | `services/pocketid` | ✓ |
| CT 109 Portainer config | Daily tar → Garage S3 `ct109-portainer-backup` → JottaCloud sync | ✓ |
| CT 111 Gitea + Coder | `services/{gitea,coder}` | ✓ | | CT 111 Gitea + Coder | `services/{gitea,coder}` | ✓ |
| VM 100 HAOS config | Phase 3 git addon → `fkrebs/ha-config` | ✗ not deployed | | VM 100 HAOS config | Phase 3 git addon → `fkrebs/ha-config` | ✗ not deployed |
| VM 100 HAOS daily tar | HA → UNAS → Backrest | ✓ | | VM 100 HAOS daily tar | HA → UNAS → Backrest | ✓ |
@@ -97,7 +99,8 @@ Immich thumbnails / encoded video, ComfyUI / Speaches models, arr-stack metadata
| Host | Data | Notes | | Host | Data | Notes |
|---|---|---| |---|---|---|
| CT 109 observe | Prometheus TSDB, Grafana dashboards, Arcane SQLite, sshwifty config | Low priority — metrics are ephemeral; dashboards can be re-exported from Grafana; add to services plan if state becomes hard to recreate | | CT 109 Prometheus TSDB, Grafana dashboards | Low priority — metrics are ephemeral; dashboards re-exportable from Grafana; add to services plan if needed |
| CT 109 Portainer data | WAL-Gstyle daily tar → `ct109-portainer-backup` Garage S3 → JottaCloud offsite sync | ✓ (via walg-offsite-sync.sh) |
--- ---
+128
View File
@@ -0,0 +1,128 @@
# Portainer BE (migrated from Arcane 2026-05-26)
Docker management UI with Portainer Business Edition license.
## Stack
- **Server**: CT 109 ("ops", 192.168.1.8), `/opt/stacks/monitoring/docker-compose.yml`, port **9000**
- **Image**: `portainer/portainer-ee:2.39.2`
- **Data volume**: `monitoring_portainer_data``/var/lib/docker/volumes/monitoring_portainer_data/_data`
- **URL**: `http://192.168.1.8:9000` (LAN-only; no Zoraxy route — access via LAN/SSH tunnel)
- **Admin user**: `fkrebs` / `tapirnase`
## License
- **Edition**: Business Edition (BE) — 3 nodes free for personal use
- **License key**: `3-QIORiAXMuBSgeYdePYgh1nuqRkvx/XWyu5D/+MQlVpvSng2CXtCG4V78212HEleOIWnIV0kK5IkpEaifea3b8NGU6o2STA0c/XXj150c/v5XSguhchCmqiXyWXDj2/+r`
- **Expires**: 2027-05-25 (365 days from issue date 2026-05-26)
- **Nodes**: 3 licensed (CT 104, CT 109 local, + 1 more)
To re-apply license (e.g. after fresh install):
```bash
curl -X POST http://192.168.1.8:9000/api/auth \
-H "Content-Type: application/json" \
-d '{"username":"fkrebs","password":"tapirnase"}' | python3 -c 'import sys,json; print(json.load(sys.stdin)["jwt"])'
# then:
curl -X POST http://192.168.1.8:9000/api/licenses/add \
-H "Authorization: Bearer <jwt>" \
-H "Content-Type: application/json" \
-d '{"license":"<key>"}'
```
## Agents (Portainer environments)
| Host | IP | Port | Status |
|---|---|---|---|
| CT 109 local | unix:///var/run/docker.sock | — | built-in |
| CT 104 | 192.168.1.40 | 9001 | `/opt/stacks/portainer-agent.yml` |
| CT 105 | 192.168.1.5 | 9001 | `/opt/stacks/ops-agents/docker-compose.yml` |
| CT 111 | 192.168.1.42 | 9001 | `/opt/stacks/ops-agents/docker-compose.yml` |
| CT 112 | 192.168.1.7 | 9001 | `/opt/stacks/ops-agents/docker-compose.yml` |
| CT 113 | 192.168.1.6 | 9001 | `/opt/stacks/db/docker-compose.yml` |
Add each as a Portainer Agent environment: `http://<ip>:9001`.
## OIDC (Pocket-ID)
**Status: pending** — requires manual OIDC client creation in Pocket-ID web UI first.
1. Go to `https://id.nuclide.systems/settings/admin/oidc-clients`
2. Create client:
- Name: `portainer`
- Redirect URIs: `http://192.168.1.8:9000/`
- Note the **Client ID** and **Client Secret**
3. Configure in Portainer → Settings → Authentication → OAuth 2.0:
- Authorization URL: `https://id.nuclide.systems/authorize`
- Access Token URL: `https://id.nuclide.systems/api/oidc/token`
- Resource URL: `https://id.nuclide.systems/api/oidc/userinfo`
- Redirect URL: `http://192.168.1.8:9000/`
- Client ID / Secret from step 2
- User Identifier: `email`
- Scopes: `openid profile email`
- Logout URL: `https://id.nuclide.systems/logout`
- Enable "Automatic user provisioning"
Or via API once client credentials are known:
```bash
JWT=$(curl -s -X POST http://192.168.1.8:9000/api/auth \
-H "Content-Type: application/json" \
-d '{"username":"fkrebs","password":"tapirnase"}' | python3 -c 'import sys,json; print(json.load(sys.stdin)["jwt"])')
curl -X PUT http://192.168.1.8:9000/api/settings \
-H "Authorization: Bearer $JWT" \
-H "Content-Type: application/json" \
-d '{
"AuthenticationMethod": 3,
"OAuthSettings": {
"ClientID": "<client-id>",
"ClientSecret": "<client-secret>",
"AuthorizationURI": "https://id.nuclide.systems/authorize",
"AccessTokenURI": "https://id.nuclide.systems/api/oidc/token",
"ResourceURI": "https://id.nuclide.systems/api/oidc/userinfo",
"RedirectURI": "http://192.168.1.8:9000/",
"LogoutURI": "https://id.nuclide.systems/logout",
"UserIdentifier": "email",
"Scopes": "openid profile email",
"OAuthAutoCreateUsers": true,
"SSO": true
}
}'
```
## Backup
- **Local S3**: daily at 01:15 UTC via `portainer-backup.timer` on CT 109
- Script: `/usr/local/sbin/portainer-backup.py`
- Bucket: `ct109-portainer-backup` on Garage (CT 104:10004)
- Key ID: `GKd4511c4a01155ebbc37aa7ff`
- Retention: 7 daily tarballs
- **Offsite**: CT 103 `walg-offsite-sync.sh` syncs `ct109-portainer-backup``jottacloud:WAL-G/ct109-portainer-backup/` daily at 02:30
Restore:
```bash
# Download latest from Garage
aws --endpoint-url http://192.168.1.40:10004 s3 ls s3://ct109-portainer-backup/
aws --endpoint-url http://192.168.1.40:10004 s3 cp s3://ct109-portainer-backup/portainer-YYYY-MM-DD.tar.gz .
tar xzf portainer-YYYY-MM-DD.tar.gz
# Replace /var/lib/docker/volumes/monitoring_portainer_data/_data/ with extracted portainer_data/
```
## Ops
```bash
# CT 109
cd /opt/stacks/monitoring
docker compose up -d --force-recreate portainer
docker logs portainer -f
# Trigger manual backup
python3 /usr/local/sbin/portainer-backup.py
```
## Arcane decommission (2026-05-26)
Arcane was replaced by Portainer on 2026-05-26:
- Arcane server (CT 109 `/opt/stacks/arcane/docker-compose.yml`) → renamed `.DECOMMISSIONED-2026-05-26`
- Arcane agents removed from: CT 104 ops-agents, CT 105 ops-agents, CT 111 ops-agents, CT 112 ops-agents, CT 113 db stack
- Arcane OIDC client `81cf4ed0-ea48-4df7-9c2d-cc1704b060f9` in Pocket-ID → to be deleted manually
- Zoraxy route `arcane.nuclide.systems` → still exists, pending explicit confirmation to remove