Troubleshooting

Start with diagnostics

codewise version
codewise doctor
codewise doctor --cluster
docker --version
kubectl version --client
helm version
kubectl config current-context

Use --require in CI when missing tools must fail the job:

codewise doctor --cluster --require docker,kubectl,helm

Dockerfile already exists

docker init refuses to overwrite an existing file. Review or rename the existing Dockerfile before generating another.

Docker daemon permission denied

Confirm Docker is running and that your user can access its daemon:

docker info

Follow your operating system's Docker post-installation guidance instead of running Codewise permanently as root.

No Kubernetes manifests found

Run from the application root and generate manifests first:

codewise k8s init --app myapp --image myapp:latest
codewise k8s apply --dry-run

Cluster unreachable or misconfigured

kubectl config get-contexts
kubectl config current-context
kubectl cluster-info

Pass a specific context with --context where supported, or update the environment's k8s.yaml.

Ask Codewise to explain the selected strategy and recovery path:

codewise env show staging
codewise deploy explain --env staging

Environment not found

codewise env list
codewise env create dev

If CODEWISE_HOME is set, Codewise reads environments from that location instead of ~/.codewise.

Output file already exists

Use a different output path or opt in to replacement:

codewise encode -i app.yaml -o app.json --force

Validate the project itself

From the Codewise repository:

make build
go test ./... -v
go test ./... -race