Louez - Docker "no tables created"

[s1nn3r]

Hi,
I tried to run the Louez docker image on Portainer.
The database looks fine:

2026-06-21 08:04:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.10-1.el9 started.
2026-06-21 08:04:38+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2026-06-21 08:04:38+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.10-1.el9 started.
2026-06-21 08:04:38+00:00 [Note] [Entrypoint]: Initializing database files
2026-06-21T08:04:38.961132Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
2026-06-21T08:04:38.967229Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.4.10) initializing of server in progress as process 81
2026-06-21T08:04:38.982949Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-06-21T08:04:40.171034Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2026-06-21T08:04:46.725289Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2026-06-21T08:04:54.415513Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
2026-06-21 08:04:54+00:00 [Note] [Entrypoint]: Database files initialized
2026-06-21 08:04:54+00:00 [Note] [Entrypoint]: Starting temporary server
2026-06-21T08:04:54.504752Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2026-06-21T08:04:54.968496Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.10) starting as process 127
2026-06-21T08:04:55.010470Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2026-06-21T08:04:56.569892Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2026-06-21T08:04:58.323570Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2026-06-21T08:04:58.323627Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2026-06-21T08:04:58.337312Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2026-06-21T08:04:58.425840Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: /var/run/mysqld/mysqlx.sock
2026-06-21T08:04:58.425936Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.4.10'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server - GPL.

When starting the Louez container I get:

▲ Next.js 16.1.6
- Local:         http://localhost:3000
- Network:       http://0.0.0.0:3000
✓ Starting...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Database Setup
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔍 Checking database configuration...
🔌 Connecting to database...
✓ Ready in 654ms
✅ Database connection successful!
📋 Checking existing tables...
📭 Database is empty. Starting initial setup...
🚀 Running database schema push (drizzle-kit push --force)...
No config path provided, using default 'drizzle.config.json'
/app/apps/web/drizzle.config.json file does not exist
🔍 Verifying database setup...
❌ Setup failed - no tables created.
❌ Database setup failed!
💡 Error: Database setup verification failed
📝 You may need to run "pnpm db:push" manually.
2026-06-21T08:08:59.747Z WARN [Better Auth]: [better-auth] Base URL could not be determined. Please set a valid base URL using the baseURL config option or the BETTER_AUTH_BASE_URL environment variable. Without this, callbacks and redirects may not work correctly.
2026-06-21T08:08:59.749Z WARN [Better Auth]: Social provider google is missing clientId or clientSecret

Any idea how to fix this?
Thanks!

[teo-goulois]

Thanks for the detailed report — the logs made this easy to track down, and you found a real bug. 🙏

What happened: on startup the app tried to initialize the empty database by shelling out to drizzle-kit push, but drizzle-kit is a dev-only tool that isn't present in the production Docker image, so no tables were ever created. Worse, the error was swallowed and the app kept running in a broken state.

Fixed in v1.8.1 (#30): the app now applies the bundled SQL migrations directly at startup — no dev tooling involved. With a fresh pull of synapsr/louez:latest (or 1.8.1), your exact Portainer setup (app container + empty MySQL, no separate migrator) will create all tables on first boot:

🚀 Running 53 pending migration(s)...
✅ All migrations completed successfully!
🎉 Your database is ready to use!

A few related improvements that ship with it:

• If database setup fails, the container now exits with a clear error instead of pretending to run — much easier to diagnose.
• /api/health returns 503 until the schema is actually ready, so orchestrator healthchecks reflect reality.
• CI now boots every image against an empty MySQL before it can be published, so this class of issue can't reach a release again.

Note: the Better Auth warnings in your log are unrelated to this bug, but you'll probably want to set BETTER_AUTH_URL (or NEXT_PUBLIC_APP_URL) so auth callbacks work correctly.

If anything still misbehaves on your side, feel free to reopen!