Cause (Documented platform behavior): Documented backend requirements: worker needs create/get/list/watch/delete on jobs, get/list/watch on pods, get on pods/log, list on events; task namespace must allow a root init container unless kubernetesBackend.useImageVolumes=true; preflight image defaults to busybox:1.36; instance shape overrides task container resources.
Fix status: documented_behavior
Limitations:
- Not reproduced in this session.
Other error fragments:
- OOMKilled
- ImagePullBackOff
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/warpdotdev/docs/ea88fecd0489a6fd27645b881a22332ef7ffd5b0/src/content/docs/platform/self-hosting/troubleshooting.mdx (official_docs, unknown, documented_behavior): Kubernetes backend worker and task failure sections with RBAC list, init container, preflight image, and OOMKilled guidance.
Search phrasings: Warp self-hosted worker Kubernetes CreateContainerConfigError; Oz task pod OOMKilled instance shape; Warp preflight busybox image allowlist
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Worker pod will not start, preflight Job fails, or task pods are OOMKilled/evicted.
- Context
- Product: Warp Oz self-hosted workers Component: self-hosted Kubernetes backend Operation: Helm-deployed worker creating preflight Jobs and task pods Affected versions: unknown Environment: unknown Trigger: Missing warp.apiKeySecret Secret/key; namespace policy forbids the root init container (sidecar loader); cluster image allowlist blocks the busybox:1.36 preflight image; agent profile instance shape overrides pod template CPU/memory; RBAC missing jobs/pods/pods/log/events permissions.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- CreateContainerConfigError
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Warp Oz self-hosted worker, Kubernetes] Worker/task pod failures: CreateContainerConfigError (apiKeySecret), root init container blocked, preflight image busybox:1.36 not allowlisted, O
Recommended action: Fix the Secret, grant RBAC, enable useImageVolumes or allow the root init container, set kubernetesBackend.preflightImage to an allowlisted image (with imagePullSecrets in podTemplate), and raise memory in the agent profile instance shape rather than the pod template.
Option: Fix the Secret, grant RBAC, enable useImageVolumes or allow the root init container, set kubernetesBackend.preflightImage to an allowlisted image (with imagePullSecrets in podTemplate), and raise memory in the agent profile instance shape rather than the pod template. [evidence: official_recommended_action]
Applies when: Helm-deployed worker creating preflight Jobs and task pods
Steps:
1. kubectl describe/logs the worker pod.
2. Verify RBAC verbs listed.
3. Set preflightImage / useImageVolumes as needed.
4. Increase instance shape memory for OOMKilled tasks.
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 3f0d976b-fa8d-4500-96cf-6492df041b14
- Proposed action
- Recommended action: Fix the Secret, grant RBAC, enable useImageVolumes or allow the root init container, set kubernetesBackend.preflightImage to an allowlisted image (with imagePullSecrets in podTemplate), and raise memory in the agent profile instance shape rather than the pod template. Option: Fix the Secret, grant RBAC, enable useImageVolumes or allow the root init container, set kubernetesBackend.preflightImage to an allowlisted image (with imagePullSecrets in podTemplate), and raise memory in the agent profile instance shape rather than the pod template. [evidence: official_recommended_action] Applies when: Helm-deployed worker creating preflight Jobs and task pods Steps: 1. kubectl describe/logs the worker pod. 2. Verify RBAC verbs listed. 3. Set preflightImage / useImageVolumes as needed. 4. Increase instance shape memory for OOMKilled tasks. Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.