Container fails to start

Edit online

If the "bawdeploy-cpe-deploy" or "bawdeploy-navigator-deploy" container fails to start, the problem is usually the binding for persistent volumes (PVs) and persistent volume claims (PVCs).

Symptoms

You might see errors like the following:

Error response from daemon: oci runtime error: container_linux.go:235: starting container process caused "container init exited prematurely"

Causes

This kind of error is caused by incorrect binding for IBM® Content Navigator or Content Platform Engine PVs and PVCs.

Resolving the problem

Delete the IBM Content Navigator or Content Platform Engine PVC, and then delete the IBM Content Navigator or Content Platform Engine related PV and NFS folders. Then, re-create them in the reverse order.