<pre><code>kubectl get pods -n abc
NAME                       READY         STATUS      RESTARTS   AGE
abc-v2-78b59ccc4f-85xgr   0/1     CrashLoopBackOff   27         129m
</code></pre>
<p>Facing below error:</p>
<pre><code>&gt; ➜  ~ kubectl logs -f abc-v2-78b59ccc4f-85xgr -n 
Error: Unable to access jarfile abc.jar
</code></pre>
<p>I am assuming either jar is not present or required access is missing.
Pls guide me here, how to proceed.</p>
<p>Edit 1: As suggested by @howard-roark, Jar is available inside container, getting the same error message.</p>
<p>Edit 2: Check results now with .jar in java command</p>
<p>Edit 4: Ideally there should be only one instance with running status.</p>

<p>Kubernetes is a Container Orchestrator.  It runs your images as Containers.  The error you are showing looks like an application error and not a Kubernetes error.  The way I would approach this is:</p>
<ol>
<li>Check if the jar file your application calls is in your image.  You can do this locally by running your image and exec'ing in to see if your jar file that your application runs is there.</li>
</ol>
<pre><code>docker run -it &lt;image&gt; /bin/bash
</code></pre>
<p>Or you can do a similar command via Kubernetes to exec into your pod:</p>
<pre><code>kubectl run -i --tty testjavacontainer --image=&lt;image&gt; -- /bin/bash
</code></pre>
<ol start="2">
<li>If it is there, then I would confirm its path and make sure that my java command is correctly referencing that path.  If it is not there, then I would adjust my Dockerfile to ensure it is at the path that my java command expects.</li>
</ol>
<p>In short, I would approach this as a <a href="https://stackoverflow.com/questions/11943948/what-causes-unable-to-access-jarfile-error">standard java error</a>, with the nuance that it happens to run in a container.</p>
