Increase Podman resources

This commit is contained in:
Jarek Rozanski 2026-09-28 11:56:17 +02:00
commit ceac06e94a
No known key found for this signature in database
3 changed files with 33 additions and 1 deletions

View file

@ -164,6 +164,17 @@ ENV PATH="${JAVA_HOME}/bin:${PNPM_HOME}/bin:${GOROOT}/bin:${GOPATH}/bin:${CARGO_
# NODE_PATH is the fallback once that climb reaches the filesystem root.
ENV NODE_PATH=/usr/local/lib/node_modules
# GRADLE_OPTS: bounds the Gradle daemon's own heap. Gradle's default heap
# auto-sizing goes off whatever memory it sees as "available" -- with no
# cap it sizes against the Makefile's --memory container ceiling in full,
# leaving nothing for the separate Kotlin-compiler daemon Gradle forks
# alongside it (see the RUN_FLAGS comment in the Makefile for the full
# story: an uncapped build here doesn't just OOM the container, it can
# starve the whole podman-machine VM). This only bounds the Gradle daemon
# itself -- a project needing the Kotlin daemon capped too should set
# `kotlin.daemon.jvmargs` in its own gradle.properties.
ENV GRADLE_OPTS="-Xmx1024m -XX:MaxMetaspaceSize=256m"
# Fixed HOME: the container is run with --userns=keep-id, so the runtime UID
# is whatever host user invoked `podman run`, which has no /etc/passwd entry
# inside the image. A plain ENV HOME is unaffected by that UID mapping, so we