The 143 exit code is related to a sigterm sended to the application container.

Seems images are pulled and things seemed correct.

When an application or command terminates or fails to execute due to a fatal error, it produces exit codes in the 128 series ( 128+n ), where n represents the signal number.

Recommended for you

The example command lines.

Despite this, the termination.

Kubernetes’s goal is to maintain the state, so it will simply restart the pod.

Usually the unix exit code is used.

But the application automatically exits and restarts with exit code 143 and error message error.

A crashloopbackoff error occurs when a pod startup fails repeatedly in kubernetes.

A pod without a command or predefined purpose might immediately exit upon starting up;

If the exit code is 0, 6 is logged.

Many jobs are throwing up exit code 137 errors and i found that it means that the container is being terminated abruptly.

The exit code is always equal to shuffling result above.

It’s not an oom issue.

But the container shutdown gracefully (even the logs are clean).

You may also like

When running a kubectl get pods command, you will see a line like this in the.

However, when i try.

I am using a containerized spring boot application in kubernetes.

The above exit code basically means the application has failed to start within the process which in turn causing failure of container.

We have a service that works fine on all probes, but got a strange exit code status of 137 with reason as error only, so i’m not sure how to debug further.

This page shows how to investigate problems related to the execution of init containers.