sko/ci-images
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
8 Commits 2 Branches 0 Tags
probe/419-ohne-daemon
Commit Graph
7 Commits
Author SHA1 Message Date
skoandClaude Opus 5.5 535b8a0f16 Probe-Workflow fuer devops #419 entfernen 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-20 09:19:59 +02:00
skoandClaude Opus 5.5 b53fadd1e6 ci-python ohne Docker-Daemon bauen: Kaniko als Docker-Schritt (devops #419)
Probe 419 - Image ohne Docker-Daemon / build (push) Successful in 1m6s
Details 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-20 09:16:55 +02:00
skoandClaude Opus 5.5 d3cd0b7263 Probe devops #419: Kaniko als Docker-Schritt statt Job-Container
Probe 419 - Image ohne Docker-Daemon / kaniko-schritt (push) Successful in 1m1s
Details 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-20 09:14:06 +02:00
skoandClaude Opus 5.5 7f4494e1cb Probe devops #419: Image ohne Docker-Daemon bauen (Kaniko, Buildah)
Probe 419 - Image ohne Docker-Daemon / kaniko (push) Failing after 13s
Details
Probe 419 - Image ohne Docker-Daemon / buildah (push) Failing after 20s
Details 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-20 09:04:43 +02:00
skoandClaude Opus 4.8 426286d190 fix: doppelten Docker-Socket-Mount entfernen (#11)
Build ci-python image / build (push) Successful in 1m6s
Details 
Der act_runner mountet /var/run/docker.sock bei docker_host:"" bereits
automatisch in den Job-Container. Unser zusaetzliches container.options
-v ...docker.sock erzeugte "Duplicate mount point: /var/run/docker.sock"
und liess den Build fehlschlagen. Docker ist im Job ohnehin verfuegbar.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-08-04 12:43:25 +02:00
skoandClaude Opus 4.8 18ac25a096 feat: Docker-Socket im ci-python-Build-Job mounten
Build ci-python image / build (push) Failing after 0s
Details 
Der Build-Job braucht einen Docker-Daemon. Statt den Socket global in jeden
Job zu mounten, fordert nur dieser Job ihn per container.options an. Setzt
voraus, dass der Runner /var/run/docker.sock in valid_volumes erlaubt
(deploy-CICD, setup-cicd-runner.yml). Ref sko/deploy-CICD#11.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-08-04 11:59:23 +02:00
skoandClaude Opus 4.8 91d216cae4 feat: ci-python CI-Basis-Image + Build-Workflow
Build ci-python image / build (push) Failing after 2m53s
Details 
Vorgebackenes Python-CI-Image (debian:bookworm-slim + uv, gepinnte CPython
3.12.13, ruff 0.16.1, pytest 9.1.1) fuer Gitea Actions. Basis + uv per Digest
gepinnt, Versionen zentral im Dockerfile-Kopf. Build-Workflow pusht
:latest + :<sha> in die Gitea-Registry (sko/ci-python), woechentlicher Rebuild.

Lokal verifiziert: Build gruen, 397 MB, uv sync --frozen + Exporter-Imports OK.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-08-04 11:21:17 +02:00