Docker image requiring mysql client and forcing ssl

[Loki-101]

Current Behavior

Note: I created a PR addressing two other known issues with the Docker image a while ago; today, I added fixes for this issue to it as well: #5324

Current Behavior:
The v1.12.0 update comes with two breaking changes to the Docker image.

First error:
Creating migration table ...................................... 16.96ms DONE

INFO Loading stored database schemas.

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

Process.php line 275:

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

Second error:

Once the mysql client is added to the image, a second error shows up if encryption is not enabled, as is the case for many single-node deployments where the database is an internal-only service:

TLS/SSL error: SSL is required, but the server does not support it

Expected Behavior

• All required packages should be included in the container image used during runtime
• SSL being off for the database should be a supported configuration with a toggle

Steps to Reproduce

• Copy https://github.com/pterodactyl/panel/blob/1.0-develop/docker-compose.example.yml onto a machine with Docker Engine
• Change the bare minimum required to run the image (I set both passwords to test123 and APP_URL to http://localhost since the test was in a local Linux VM with a web browser)
• docker compose up -d
• Wait 10-20 seconds
• docker compose logs panel

To produce the second error, you can either add the mysql client in the image or temporarily in the container

• docker compose exec panel apk add mysql-client
• docker compose restart panel
• Wait 5-10 seconds
• docker compose logs panel

Panel Version

v1.12.0

Wings Version

N/A

Games and/or Eggs Affected

N/A

Docker Image

N/A

Error Logs

Error 1: https://ptero.co/kurigiceno
Error 2 (after adding client): https://ptero.co/elixudodaz

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.

[rathmerdominik]

I second this.
had the same issue

[Kairosen]

I third this.
Same exact issue.

[Kairosen]

Is there a temporary workaround for this for now? Like using a different pterodactyl image version?

[Loki-101]

@Kairosen Yes, there is. This specific issue with v1.12.0 only appears on fresh installs, not on migrations. Use the v1.11.11 tag, set up the panel, then take the container fully down and change the image to v1.12.0; the migration should go through without issues.

Credit to @danny6167 for pointing that workaround out in the Discord server.

[tylerhsteiner]

There doesn't appear to be a way to specify the older tag when trying to deploy via the TrueNAS apps system, so I guess I'll just patiently wait until the fix is accepted. I'd just run across Pterodactyl and thought it would be a very tidy way to manage my various game servers that I run off of my TrueNAS so I don't have an old version to fall back on.

[kalszko]

There doesn't appear to be a way to specify the older tag when trying to deploy via the TrueNAS apps system, so I guess I'll just patiently wait until the fix is accepted. I'd just run across Pterodactyl and thought it would be a very tidy way to manage my various game servers that I run off of my TrueNAS so I don't have an old version to fall back on.

I was able to get v1.11.11 working on TrueNAS by installing the latest one using the pre made installer, then conveting it to a custom app, then changing the YAML file line 167 to: image: ghcr.io/pterodactyl/panel:v1.11.11. Hopfully this helps as a temporary fix.

[Insan3ludi]

There doesn't appear to be a way to specify the older tag when trying to deploy via the TrueNAS apps system, so I guess I'll just patiently wait until the fix is accepted. I'd just run across Pterodactyl and thought it would be a very tidy way to manage my various game servers that I run off of my TrueNAS so I don't have an old version to fall back on.

I was able to get v1.11.11 working on TrueNAS by installing the latest one using the pre made installer, then conveting it to a custom app, then changing the YAML file line 167 to: image: ghcr.io/pterodactyl/panel:v1.11.11. Hopfully this helps as a temporary fix.

This seems to be a viable way. but is there any downside to converting it to a custom app? it specifically warns you that this step is not reversible :/

[tylerhsteiner]

There doesn't appear to be a way to specify the older tag when trying to deploy via the TrueNAS apps system, so I guess I'll just patiently wait until the fix is accepted. I'd just run across Pterodactyl and thought it would be a very tidy way to manage my various game servers that I run off of my TrueNAS so I don't have an old version to fall back on.

I was able to get v1.11.11 working on TrueNAS by installing the latest one using the pre made installer, then conveting it to a custom app, then changing the YAML file line 167 to: image: ghcr.io/pterodactyl/panel:v1.11.11. Hopfully this helps as a temporary fix.

This seems to be a viable way. but is there any downside to converting it to a custom app? it specifically warns you that this step is not reversible :/

The biggest downside I believe is that all the items that would normally be managed with the App Catalog are no longer managed (e.g. updates/version, new/changed variables, [default] configuration changes, etc.). I run ~15 apps, of which 3 are custom (from the start, not converted) and definitely not as easily managed.

While it would be a temporary workaround, since I haven't started with pterodactyl yet, I decided to wait until the update gets done/accepted and it makes it into the App Catalog (usually overnight once published I believe).

[danny6167]

Here's a quick and easy way to get around this issue on TrueNAS. No need to convert it to a custom app.

Just access the pterodactyl container shell using the TrueNAS WebUI, and run the following

apk add mariadb-client
php artisan migrate --force --seed

It will complete the database setup and everything should work.

Regular docker users can do the same thing by using docker exec to get into their containers and running the commands.

[Insan3ludi]

Here's a quick and easy way to get around this issue on TrueNAS. No need to convert it to a custom app.

Just access the pterodactyl container shell using the TrueNAS WebUI, and run the following

apk add mariadb-client
php artisan migrate --force --seed
It will complete the database setup and everything should work.

Regular docker users can do the same thing by using docker exec to get into their containers and running the commands.

This did the trick! Thanks a lot :)