title: Prisma: All migrations are already applied
body: <p>Goal: Run DB migrations inside an InitContainer in a Kubernetes cluster to update the DB.</p>
  <p>Expected Result: The container should run, with the Prisma migration packaged into the container. Subsequently, the Prisma migrate command should run and update the DB,</p>
  <pre><code>npx prisma migrate up --experimental
  </code></pre>
  <p>At the moment when the DB is empty the container runs, the migrate command is called and I receive the following message,</p>
  <pre><code>All migrations are already applied
  </code></pre>
  <p>Whilst this creates the _Migration table in the DB none of the migrations are applied. If I connected to the DB from my local machine I can run the migrate scripts and everything updates. If I run the migrate script again from within the container I get the following error,</p>
  <pre><code>Error: There are more migrations in the database than locally. This must not happen. Local migration ids: . Remote migration ids
  </code></pre>
  <p>To ensure I was connecting to the DB correctly I ran,</p>
  <pre><code>npx prisma introspect --print
  </code></pre>
  <p>This printed out the DB schema from the database to prove that the connection string baked into the container was actually hitting the right DB.</p>
  <p>I am a little stumped now about where the issue might be. Does anyone know how best to debug Prisma migrations or are there any known issues that might have caused this problem?</p>