DT
Drizzle Team•2w ago
JROCBABY

Double Slash in Path Causes ENOENT Error When Running Migrations in Docker

Hi everyone, I’m encountering an issue with Drizzle Kit when running migrations in a Docker container. The error occurs because Drizzle Kit is trying to read the 0000_snapshot.json file using a path with a double slash (//), like this: ENOENT: no such file or directory, open './/app/apps/my-app/src/drizzle/meta/0000_snapshot.json' The file exists at the correct path (/app/apps/my-app/src/drizzle/meta/0000_snapshot.json), but the double slash seems to be causing the issue. Here’s what I’ve tried so far: Verified that the schema.ts file is correct and the migration files are generated properly. Used path.resolve and path.normalize in drizzle.config.ts to ensure paths are correct. Confirmed that the snapshot file exists in the container at the expected location. Here’s my drizzle.config.ts: 
Copy
import { defineConfig } from 'drizzle-kit';
import * as path from 'path';

const schemaPath = path.resolve(__dirname, './src/db/schema.ts');
const outPath = path.resolve(__dirname, './src/drizzle');

export default defineConfig({
  dialect: 'postgresql',
  schema: schemaPath,
  out: outPath,
  dbCredentials: {
    host: process.env.DB_HOST,
    port: Number(process.env.DB_PORT),
    user: process.env.DB_USER,
    password: process.env.DB_PASSWORD,
    database: process.env.DB_NAME,
    ssl: false,
  },
});
Copy
import { defineConfig } from 'drizzle-kit';
import * as path from 'path';

const schemaPath = path.resolve(__dirname, './src/db/schema.ts');
const outPath = path.resolve(__dirname, './src/drizzle');

export default defineConfig({
  dialect: 'postgresql',
  schema: schemaPath,
  out: outPath,
  dbCredentials: {
    host: process.env.DB_HOST,
    port: Number(process.env.DB_PORT),
    user: process.env.DB_USER,
    password: process.env.DB_PASSWORD,
    database: process.env.DB_NAME,
    ssl: false,
  },
});
And here’s the relevant part of my docker-compose.yml: 
Copy
command: >
  sh -c "cd /app/apps/my-app &&
         bunx drizzle-kit generate --config drizzle.config.ts &&
         bunx drizzle-kit migrate"
Copy
command: >
  sh -c "cd /app/apps/my-app &&
         bunx drizzle-kit generate --config drizzle.config.ts &&
         bunx drizzle-kit migrate"
It seems to be caused by 
 const raw2 = JSON.parse((0, import_fs.readFileSync)(./${it}).toString());
 const raw2 = JSON.parse((0, import_fs.readFileSync)(./${it}).toString());
Can't we fix it by doing 
const raw2 = JSON.parse((0, import_fs.readFileSync)(path.normalize(`${it}`)).toString());
const raw2 = JSON.parse((0, import_fs.readFileSync)(path.normalize(`${it}`)).toString());
Has anyone encountered this issue before? Is there a way to prevent Drizzle Kit from introducing the double slash in the path? Any help would be greatly appreciated!
1 Reply
JROCBABY
JROCBABYOP•2w ago
Here is an example 
const fs = require('fs');
const path = require('path');

// Mock the file content
fs.writeFileSync('0000_snapshot.json', JSON.stringify({ key: 'value' }));

// Simulate the `it` variable (path to the snapshot file)
const it = './0000_snapshot.json';

// Normalize the path
const normalizedPath = path.normalize(`./${it}`);

console.log('Original Path:', it);
console.log('Normalized Path:', normalizedPath);

// Try to read the file
try {
  const raw2 = JSON.parse(fs.readFileSync(normalizedPath).toString());
  console.log('File read successfully:', raw2);
} catch (error) {
  console.error('Error reading file:', error);
}
const fs = require('fs');
const path = require('path');

// Mock the file content
fs.writeFileSync('0000_snapshot.json', JSON.stringify({ key: 'value' }));

// Simulate the `it` variable (path to the snapshot file)
const it = './0000_snapshot.json';

// Normalize the path
const normalizedPath = path.normalize(`./${it}`);

console.log('Original Path:', it);
console.log('Normalized Path:', normalizedPath);

// Try to read the file
try {
  const raw2 = JSON.parse(fs.readFileSync(normalizedPath).toString());
  console.log('File read successfully:', raw2);
} catch (error) {
  console.error('Error reading file:', error);
}

Did you find this page helpful?