title: How to get into Docker image filesystem when Container Won't run
body: <p>What's the best way to troubleshoot a container which won't start that fails on a filepath?  I need to peak into the image somehow and list out and see if the directories and what file structure is actually internal to the container/image after I start it but if it fails to start I'm sorta out of luck right?</p>
  <pre><code>▶ PORT=8080 &amp;&amp; docker run -p 9090:${PORT} -e PORT=${PORT} gcr.io/ssss/s@sha256:5ad05d1d37baae8f548b08a41fa7c5d69465adb8acd4cc9b1703f2ed4ee361ec
  Unable to find image 'gcr.io/ssss-1349/ssss@sha256:5ad05d1d37baae8f548b08a41fa7c5d69465adb8acd4cc9b1703f2ed4ee361ec' locally
  sha256:5ad05d1d37baae8f548b08a41fa7c5d69465adb8acd4cc9b1703f2ed4ee361ec: Pulling from ssss-1349/ssss
  cbdbe7a5bc2a: Already exists
  15f7fe915f93: Already exists
  3cae4fa026a7: Already exists
  bfa729779926: Already exists
  db6f693f3456: Pull complete
  2e4c635245d4: Pull complete
  6017db5d3271: Pull complete
  Digest: sha256:5ad05d1d37baae8f548b08a41fa7c5d69465adb8acd4cc9b1703f2ed4ee361ec
  Status: Downloaded newer image for gcr.io/ssss-1349/ssss@sha256:5ad05d1d37baae8f548b08a41fa7c5d69465adb8acd4cc9b1703f2ed4ee361ec
  yarn run v1.22.4
  $ node --optimize_for_size --trace-warnings --experimental-json-modules --no-warnings ./server/server.js
  internal/modules/cjs/loader.js:1083
    throw err;
    ^
  
  Error: Cannot find module '/dist/server/server.js'
      at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1080:15)
      at Function.Module._load (internal/modules/cjs/loader.js:923:27)
      at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
      at internal/main/run_main_module.js:17:47 {
    code: 'MODULE_NOT_FOUND',
    requireStack: []
  }
  error Command failed with exit code 1.
  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
  </code></pre>
  <p>It's saying <code>'/dist/server/server.js'</code> is not there but I know it has to be, I copied it and so I need to peak inside the OS of the container and look around somehow to see what the file structure actually is to try to troubleshoot it</p>
  <p><strong>Dockerfile</strong>:</p>
  <pre><code>FROM node:14.8.0-alpine
  ENV PORT 8080
  WORKDIR dist
  RUN yarn
  COPY . ./
  CMD [ &quot;yarn&quot;, &quot;start&quot; ]
  </code></pre>