k.rennerandClaude Opus 4.7
ff33f03ebd
ci/woodpecker/push/deploy-infrastructure Pipeline was successful
ci/woodpecker/push/security-scan Pipeline failed
ci/woodpecker/manual/deploy-infrastructure Pipeline was successful
ci/woodpecker/manual/build-caddy Pipeline failed
ci/woodpecker/manual/build-ci-images Pipeline is running
Pipeline 832 (build-ci-images) ran 4 kaniko builds in parallel across 2 agents (woodpecker_agent_count=2). build-ansible got OOM- killed — 2 GiB per agent split across 2 concurrent kaniko jobs is ~1 GiB per build, and ansible + collections + pip deps under kaniko's tmpfs layer cache exceeded that. 4 GiB per agent gives ~2 GiB per concurrent build, which has enough headroom for the largest of the four images. If we ever hit the same wall again the next bump is doubling the agent count, not the memory — kaniko parallelism doesn't help much beyond ~2 GiB. BPG's proxmox_virtual_environment_container does in-place memory updates for LXC (cgroup-level, no restart), so the apply is safe to run while the agents are servicing other jobs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>