docs: document DOCKER_REGISTRY fix in session log and update .env
- Added details to the 2026-03-10 session log about the DOCKER_REGISTRY root cause and resolution. - Updated `.env` to correct the DOCKER_REGISTRY path (`/meldestelle` segment added) for proper Docker image resolution. - Included related screenshots for troubleshooting and fix verification. Signed-off-by: Stefan Mogeritsch <stefan.mo.co@gmail.com>
This commit is contained in:
@@ -14,7 +14,7 @@ BACKUP_RETENTION_DAYS=7
|
|||||||
|
|
||||||
# Docker build versions (optional overrides)
|
# Docker build versions (optional overrides)
|
||||||
DOCKER_VERSION=1.0.0-SNAPSHOT
|
DOCKER_VERSION=1.0.0-SNAPSHOT
|
||||||
DOCKER_REGISTRY=git.mo-code.at/mocode-software
|
DOCKER_REGISTRY=git.mo-code.at/mocode-software/meldestelle
|
||||||
DOCKER_BUILD_DATE=2026-02-02T15:00:00Z
|
DOCKER_BUILD_DATE=2026-02-02T15:00:00Z
|
||||||
DOCKER_GRADLE_VERSION=9.3.1
|
DOCKER_GRADLE_VERSION=9.3.1
|
||||||
# Check if 25 is intended (Early Access) or if LTS 21 was meant
|
# Check if 25 is intended (Early Access) or if LTS 21 was meant
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# Session Log — 2026-03-10: Keycloak Hostname Fix & Git Push Analyse
|
# Session Log — 2026-03-10: Keycloak Hostname Fix, Git Push Analyse & DOCKER_REGISTRY Fix
|
||||||
|
|
||||||
**Datum:** Di. 10. März 2026
|
**Datum:** Di. 10. März 2026
|
||||||
**Agent:** 🧹 Curator / 👷 Backend Developer
|
**Agent:** 🧹 Curator / 👷 Backend Developer
|
||||||
@@ -13,6 +13,7 @@
|
|||||||
| 1 | Git Push fehlgeschlagen | ✅ Analysiert (Netzwerkfehler) |
|
| 1 | Git Push fehlgeschlagen | ✅ Analysiert (Netzwerkfehler) |
|
||||||
| 2 | Keycloak Admin-Dashboard auf `meldestelle-host` nicht erreichbar | ✅ Root Cause + Fix dokumentiert |
|
| 2 | Keycloak Admin-Dashboard auf `meldestelle-host` nicht erreichbar | ✅ Root Cause + Fix dokumentiert |
|
||||||
| 3 | Alertmanager Permission-Fehler | ✅ Identifiziert |
|
| 3 | Alertmanager Permission-Fehler | ✅ Identifiziert |
|
||||||
|
| 4 | `DOCKER_REGISTRY` falsch — Images nicht gefunden | ✅ Behoben |
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
@@ -153,10 +154,68 @@ docker compose -f dc-ops.yaml restart alertmanager
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
## Problem 4: `DOCKER_REGISTRY` falsch — Images nicht gefunden
|
||||||
|
|
||||||
|
**Zeitpunkt:** 2026-03-10 ~13:20
|
||||||
|
|
||||||
|
### Symptom
|
||||||
|
|
||||||
|
```
|
||||||
|
! Image git.mo-code.at/mocode-software/keycloak:latest manifest unknown
|
||||||
|
! Image git.mo-code.at/mocode-software/api-gateway:latest manifest unknown
|
||||||
|
Error response from daemon: No such image: git.mo-code.at/mocode-software/keycloak:latest
|
||||||
|
```
|
||||||
|
|
||||||
|
`docker compose --profile all up -d --no-build` schlug fehl — alle custom Images nicht gefunden.
|
||||||
|
|
||||||
|
### Root Cause: Falscher Registry-Pfad in `.env`
|
||||||
|
|
||||||
|
Die Pipeline (`.gitea/workflows/docker-publish.yaml`) pusht Images nach:
|
||||||
|
|
||||||
|
```
|
||||||
|
10.0.0.22:3000/mocode-software/meldestelle/keycloak:latest
|
||||||
|
^^^^^^^^^^^^
|
||||||
|
```
|
||||||
|
|
||||||
|
Die `.env` hatte jedoch:
|
||||||
|
|
||||||
|
```env
|
||||||
|
DOCKER_REGISTRY=git.mo-code.at/mocode-software # ← /meldestelle fehlt!
|
||||||
|
```
|
||||||
|
|
||||||
|
Docker suchte also unter `git.mo-code.at/mocode-software/keycloak:latest` — das `/meldestelle/`-Segment fehlte.
|
||||||
|
|
||||||
|
### Fix
|
||||||
|
|
||||||
|
| Datei | Vorher | Nachher |
|
||||||
|
|-------|--------|---------|
|
||||||
|
| `.env` (lokal) | `git.mo-code.at/mocode-software` | `git.mo-code.at/mocode-software/meldestelle` |
|
||||||
|
|
||||||
|
### Anwendung auf `meldestelle-host`
|
||||||
|
|
||||||
|
```bash
|
||||||
|
nano .env
|
||||||
|
# DOCKER_REGISTRY=git.mo-code.at/mocode-software
|
||||||
|
# ↓
|
||||||
|
# DOCKER_REGISTRY=git.mo-code.at/mocode-software/meldestelle
|
||||||
|
|
||||||
|
docker compose --profile all up -d --no-build
|
||||||
|
```
|
||||||
|
|
||||||
|
### Gelernt
|
||||||
|
|
||||||
|
> Der Image-Pfad in `DOCKER_REGISTRY` muss exakt dem Pfad entsprechen, unter dem die Pipeline
|
||||||
|
> die Images in die Registry pusht — inklusive aller Namespace-Segmente (`/meldestelle/`).
|
||||||
|
> Beim Einrichten einer neuen Registry immer `docker pull <full-image-path>` manuell testen,
|
||||||
|
> bevor `docker compose up --no-build` verwendet wird.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
## Offene Punkte
|
## Offene Punkte
|
||||||
|
|
||||||
| Punkt | Priorität | Beschreibung |
|
| Punkt | Priorität | Beschreibung |
|
||||||
|---------------------------------------|------------|--------------------------------------------------------|
|
|---------------------------------------|------------|-----------------------------------------------------------------|
|
||||||
| Keycloak Hostname Fix anwenden | 🔴 Hoch | `.env` auf `meldestelle-host` korrigieren |
|
| Keycloak Hostname Fix anwenden | 🔴 Hoch | `.env` auf `meldestelle-host`: `KC_HOSTNAME=10.0.0.50:8180` |
|
||||||
| Alertmanager Permission Fix | 🟡 Mittel | `chmod 644` auf alertmanager.yaml |
|
| DOCKER_REGISTRY Fix anwenden | 🔴 Hoch | `.env` auf `meldestelle-host`: `DOCKER_REGISTRY=...meldestelle` |
|
||||||
| `KC_HOSTNAME_STRICT_HTTPS` bereinigen | 🟢 Niedrig | Deprecated Variable aus allen `.env`-Dateien entfernen |
|
| Alertmanager Permission Fix | 🟡 Mittel | `chmod 644` auf alertmanager.yaml |
|
||||||
|
| `KC_HOSTNAME_STRICT_HTTPS` bereinigen | 🟢 Niedrig | Deprecated Variable aus allen `.env`-Dateien entfernen |
|
||||||
|
|||||||
Binary file not shown.
|
After Width: | Height: | Size: 192 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 242 KiB |
Reference in New Issue
Block a user