Panel v1.12.x Docker image fails during schema load – `mysql: not found`

[Carlito53]

Current Behavior

When deploying the panel using the official Docker image:

ghcr.io/pterodactyl/panel:latest

or

ghcr.io/pterodactyl/panel:v1.12.1

The container connects successfully to MariaDB, but fails during schema loading with:

database/schema/mysql-schema.sql ... FAIL
sh: mysql: not found
Exit Code: 127 (Command not found)

This results in a 500 Server Error and prevents the panel from starting properly.

Expected Behavior

Panel should initialize the database successfully without requiring the mysql CLI binary inside the container.

Steps to Reproduce

Deploy panel with Docker (v1.12.x or latest)

Use standard MariaDB (10.11 / 11.x)

Start stack

Check logs → failure during schema import

Panel Version

1.12.1

Wings Version

1.12.0

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

ln: /var/log/panel/logs: File exists
external vars exist.
Checking if https is required.
Checking if letsencrypt email is set.
No letsencrypt email is set using http config.
Removing the default nginx config
Checking database status.
Waiting for database connection...
Waiting for database connection...
Waiting for database connection...
Waiting for database connection...
Waiting for database connection...
Waiting for database connection...
Waiting for database connection...
Waiting for database connection...
ptero-mariadb (172.21.0.11:3306) open
Migrating and Seeding D.B

   INFO  Preparing database.

  Creating migration table ...................................... 23.64ms DONE

   INFO  Loading stored database schemas.

  database/schema/mysql-schema.sql .............................. 21.77ms FAIL

In Process.php line 280:

  The command "mysql  --user="${:LARAVEL_LOAD_USER}" --password="${:LARAVEL_L
  OAD_PASSWORD}" --host="${:LARAVEL_LOAD_HOST}" --port="${:LARAVEL_LOAD_PORT}
  " --database="${:LARAVEL_LOAD_DATABASE}" < "${:LARAVEL_LOAD_PATH}"" failed.

  Exit Code: 127(Command not found)

  Working directory: /app

  Output:
  ================


  Error Output:
  ================
  sh: mysql: not found


Starting cron jobs.
Starting supervisord.
2026-02-27 15:57:20,965 CRIT Server 'unix_http_server' running without any HTTP authentication checking

Is there an existing issue for this?

• I have searched the existing issues before opening this issue. I understand that maintainers may close this issue without communication if I have not provided sufficient information.

[Ghosterers]

This happens because the official Docker image does not include the MySQL client binary, but the entrypoint tries to run:

mysql --user=... --password=...

Since mysql is missing, the schema load fails with:

sh: mysql: not found
Exit Code: 127

---

✅ Recommended Permanent Fix (Custom Image)

1️⃣ Create a Dockerfile

In the same directory as your docker-compose.yml, create a file named:

Dockerfile

Add:

FROM ghcr.io/pterodactyl/panel:v1.12.1
RUN apk add --no-cache mysql-client

This installs the missing MySQL CLI inside the container.

---

2️⃣ Modify docker-compose.yml

Change your panel service from:

image: ghcr.io/pterodactyl/panel:v1.12.1

to:

build: .
image: ghcr.io/pterodactyl/panel:v1.12.1-mysqlcli

Your panel service should look similar to:

services:
  panel:
    build: .
    image: ghcr.io/pterodactyl/panel:v1.12.1-mysqlcli
    restart: always
    env_file:
      - .env
    volumes:
      - ./panel-data:/app
    depends_on:
      - mariadb

(Keep your existing ports, environment variables, volumes, etc.)

---

3️⃣ Rebuild and Restart

Run:

docker compose down
docker compose build --no-cache panel
docker compose up -d
docker compose logs -f panel

You should now see:

database/schema/mysql-schema.sql ... DONE

instead of FAIL.

---

⚡ Quick Temporary Fix (Not Recommended for Production)

If you need a fast workaround:

docker compose exec panel apk add --no-cache mysql-client
docker compose restart panel

⚠️ This will break again if the container is recreated.

---

🔒 Best Practice

• Do NOT use :latest in production.
• Pin a specific version like v1.12.1.
• Always test updates in staging before upgrading.

---

If you paste your full docker-compose.yml, I can try yo rewrite it cleanly for your setup (without affecting Wings or MariaDB).

[AdamT20054]

Also experiencing the same on :latest or :1.12.1

[stav3ng3r]

I tried @Ghosterers Dockerfile fix on :latest and ::1.12.1 but now I'm getting:

panel-1     |   Error Output:                                                                
panel-1     |   ================                                                             
panel-1     |   mysql: Deprecated program name. It will be removed in a future release, use  
panel-1     |    '/usr/bin/mariadb' instead                                                  
panel-1     |   ERROR 2026 (HY000): TLS/SSL error: SSL is required, but the server does not  
panel-1     |    support it 

[keksgauner]

MariaDB removed the MySQL command in the mariadb docker.
The command is now mariadb and have the same functionality and so on.
f.e.
Old: docker compose exec database mysql -u root -p
New: docker compose exec database mariadb -u root -p

There is already an MariaDB connector in pterodactyl.

panel/config/database.php

Lines 63 to 87 in 0f82c10

	'mariadb' => [
	'driver' => 'mariadb',
	'url' => env('DB_URL', env('DATABASE_URL')),
	'host' => env('DB_HOST', '127.0.0.1'),
	'port' => env('DB_PORT', '3306'),
	'database' => env('DB_DATABASE', 'panel'),
	'username' => env('DB_USERNAME', 'pterodactyl'),
	'password' => env('DB_PASSWORD', ''),
	'unix_socket' => env('DB_SOCKET', ''),
	'charset' => env('DB_CHARSET', 'utf8mb4'),
	'collation' => env('DB_COLLATION', 'utf8mb4_unicode_ci'),
	'prefix' => env('DB_PREFIX', ''),
	'prefix_indexes' => true,
	'strict' => env('DB_STRICT_MODE', true),
	'engine' => null,
	'timezone' => env('DB_TIMEZONE', Time::getMySQLTimezoneOffset(env('APP_TIMEZONE', 'UTC'))),
	'sslmode' => env('DB_SSLMODE', 'prefer'),
	'options' => extension_loaded('pdo_mysql') ? array_filter([
	PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
	PDO::MYSQL_ATTR_SSL_CERT => env('MYSQL_ATTR_SSL_CERT'),
	PDO::MYSQL_ATTR_SSL_KEY => env('MYSQL_ATTR_SSL_KEY'),
	PDO::MYSQL_ATTR_SSL_VERIFY_SERVER_CERT => env('MYSQL_ATTR_SSL_VERIFY_SERVER_CERT', true),
	]) : [],
	],
	],

I think in the panel environment should include:
DB_CONNECTION: "mariadb"

The migrations don't work with this setting by me:

panel-1     |   2020_04_04_131016_add_table_server_transfers ................. 163.34ms DONE
panel-1     |   2020_04_10_141024_store_node_tokens_as_encrypted_value ....... 151.77ms FAIL
panel-1     | 
panel-1     | In Connection.php line 825:
panel-1     |                                                                                
panel-1     |   SQLSTATE[42S22]: Column not found: 1054 Unknown column '`daemonSecret`' in   
panel-1     |   'nodes' (Connection: mariadb, SQL: alter table `nodes` rename column ```dae  
panel-1     |   monSecret``` to `daemon_token`)                                              
panel-1     |                                                                                
panel-1     | 
panel-1     | In Connection.php line 571:
panel-1     |                                                                                
panel-1     |   SQLSTATE[42S22]: Column not found: 1054 Unknown column '`daemonSecret`' in   
panel-1     |   'nodes'                                                                      
panel-1     |                                                                                
panel-1     | 
panel-1     | Starting cron jobs.
panel-1     | Starting supervisord.
panel-1     | 2026-03-11 08:53:55,702 CRIT Server 'unix_http_server' running without any HTTP authentication checking

But I think this is my problem.

[cmasters457]

@keksgauner thank you, adding DB_CONNECTION: "mariadb" into the default docker-compose example here

resolved my issue

    environment:
      <<: [*panel-environment, *mail-environment]
      DB_PASSWORD: *db-password
      APP_ENV: "production"
      APP_ENVIRONMENT_ONLY: "false"
      CACHE_DRIVER: "redis"
      RECAPTCHA_ENABLED: "false"
      SESSION_DRIVER: "redis"
      QUEUE_DRIVER: "redis"
      REDIS_HOST: "cache"
      DB_CONNECTION: "mariadb"
      DB_HOST: "database"
      DB_PORT: "3306"

[keksgauner]

@Ghosterers

Best Practice is good but did you used an LLM?

To install MySQL on an MariaDB image is bad.
It's better to use the MySQL image.

This is basically just a botched solution, even though there could be a very simple fix.

MariaDB is not 100% the same as MySQL.

The fixes suggested there should not be used in the production system.

#5595 (comment)
is a better solution.

I think we should pull this into the example file.