<p>I have mounted a binary (tini init) to the <code>/executables</code> mountPath. The docker image is <code>busybox:latest</code></p>

<p>Mounting:</p>

<pre><code>- name: executables
  mountPath: /executables
</code></pre>

<p>Volume creation:</p>

<pre><code>- name: executables
  emptyDir: {}
</code></pre>

<p>I ran a sidecar container that adds the <code>tini</code> binary to this volume.</p>

<p>inside the <code>/executables</code> directory after attaching to the container:</p>

<pre class="lang-sh prettyprint-override"><code>/executables # ls
tini
/executables # pwd
/executables
/executables # ls
tini
/executables # ./tini 
sh: ./tini: not found
/executables # 
</code></pre>

<p>Everything's alright but when I try executing it, it shows <code>not found</code> when the file is right there! driving me nuts. Please help!</p>

Hrishikesh
<p>Solved this using a static build for the binary, turns out it's very relevant to this:  <a href="https://unix.stackexchange.com/questions/18061/why-does-sh-say-not-found-when-its-definitely-there">https://unix.stackexchange.com/questions/18061/why-does-sh-say-not-found-when-its-definitely-there</a></p>
