kaniko with AI
6.3K
kaniko-revanced is an actively maintained, high-performance, and drop-in compatible continuation of the original Google Kaniko (GoogleContainerTools/kaniko). It executes container image builds from a Dockerfile inside a container or Kubernetes cluster without requiring a Docker daemon or privileged security contexts.
All images are multi-architecture (linux/amd64, linux/arm64, linux/s390x, linux/ppc64le).
| Image Tag | Flavor | Shell Included | Cloud Credential Helpers | Recommended Use Case |
|---|---|---|---|---|
0.2.0, latest | Standard | ❌ | GCR, ECR, ACR | Production & Kubernetes: Zero-overhead, minimal attack surface without shell binaries. |
debug-0.2.0, debug | Debug | ✅ (/busybox/sh) | GCR, ECR, ACR | GitLab CI & CI/CD Pipelines: Required when your CI runner executes script steps inside the container. |
slim-0.2.0, slim | Slim | ❌ | ❌ | Minimal Footprint: Lightweight image when cloud credential helpers are not required. |
ai | AI Edition | ❌ | GCR, ECR, ACR | Autonomous Production: Intelligent auto-healing, diagnostics, and optimization. |
ai-debug | AI Debug | ✅ (/busybox/sh) | GCR, ECR, ACR | Interactive AI CI/CD: Full shell plus AI auto-healing and diagnostic reports. |
kaniko-revanced includes native AI intelligence directly inside the builder. It connects to any OpenAI-compatible endpoint (Local Ollama, Google Gemini, OpenAI, Anthropic, Groq, DeepSeek, OpenRouter, or enterprise gateways).
--llm-auto-heal): Catches failing RUN/COPY steps in real-time, prompts the LLM for a validated fix, prints a colorized unified diff, and automatically retries the build up to --llm-max-retries=N.--llm-diagnose): Pinpoints the exact root-cause of build failures, suggests image size reductions (multi-stage builds, cache purging), and audits security misconfigurations.--llm-diagnose-apply): Translates optimization advice into a production-ready patched Dockerfile.\e[0Ksection_start...) to prevent exceeding GitLab's 4MB job log limit..gitlab-ci.yml)build:
stage: build
image:
name: kanikorevanced/executor:debug
entrypoint: [""]
script:
- mkdir -p /kaniko/.docker
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
- /kaniko/executor
--context "${CI_PROJECT_DIR}"
--dockerfile "${CI_PROJECT_DIR}/Dockerfile"
--destination "${CI_REGISTRY_IMAGE}:${CI_COMMIT_TAG:-latest}"
build-with-ai:
stage: build
image:
name: kanikorevanced/executor:ai-debug
entrypoint: [""]
variables:
KANIKO_LLM_API: "https://api.groq.com/openai/v1"
KANIKO_LLM_KEY: "$GROQ_API_KEY"
KANIKO_LLM_MODEL: "llama-3.3-70b-versatile"
KANIKO_LLM_AUTO_HEAL: "true"
KANIKO_LLM_DIAGNOSE: "true"
script:
- mkdir -p /kaniko/.docker
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
- /kaniko/executor
--context "${CI_PROJECT_DIR}"
--dockerfile "${CI_PROJECT_DIR}/Dockerfile"
--destination "${CI_REGISTRY_IMAGE}:latest"
apiVersion: v1
kind: Pod
metadata:
name: kaniko-builder
spec:
containers:
- name: kaniko
image: kanikorevanced/executor:latest
args:
- "--context=git://github.com/my-org/my-repo.git#refs/heads/main"
- "--destination=myregistry.azurecr.io/my-app:latest"
volumeMounts:
- name: docker-config
mountPath: /kaniko/.docker
restartPolicy: Never
volumes:
- name: docker-config
secret:
secretName: regcred
items:
- key: .dockerconfigjson
path: config.json
docker run --rm -it --net=host \
-v $(pwd):/workspace \
kanikorevanced/executor:ai \
--context /workspace \
--dockerfile /workspace/Dockerfile \
--no-push \
--llm-auto-heal \
--llm-api="http://localhost:11434/v1" \
--llm-model="qwen2.5-coder:7b"
In benchmark comparisons against upstream Google Kaniko on complex multi-stage workloads:
sync.Pool memory allocation and optimized tar serialization.gcr.io/kaniko-project/executor without modifying arguments.Content type
Image
Digest
sha256:52b82c53f…
Size
28.7 MB
Last updated
6 days ago
docker pull kanikorevanced/executor