[BUG] ENV VARS not working as expected, out of date?

[iamkevinmccarthy]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

My use case is utilizing the PMA_HOSTS and PMA_VERBOSES variables. I set a handful of servers and their verbose names, and I don't get a dropdown to select which one I want to connect to. I tried this with the standard Phpmyadmin Docker and it works fine.

Also, the VARS available from the official PMA Docker repo is significantly larger than what's available here (it's mostly SSL related but that can be pretty important). Please update this accordingly.

NOTE: I disabled PMA_ARBITRARY for this.

Expected Behavior

When variables such as PMA_HOSTS and PMA_VERBOSES are set, there should be a USER and PASS field, followed by a SERVER CHOICE dropdown. See below.

Steps To Reproduce

• Deploy a fresh install of this image.
• Add a new var for PMA_HOSTS and enter 2 or more hosts to connect to (comma separated)
• Add a new var for PMA_VERBOSES and enter an equal amount of verbose server names
• Redeploy
• Refresh PMA

Environment

- OS: Ubuntu 24.04
- How docker service was installed: Via Coolify dashboard, which uses the `image: lscr.io/linuxserver/phpmyadmin:latest`

CPU architecture

x86-64

Docker creation

services:
  phpmyadmin:
    image: 'lscr.io/linuxserver/phpmyadmin:latest'
    environment:
      - SERVICE_FQDN_PHPMYADMIN
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Madrid
      - PMA_ARBITRARY=1
      - PMA_ABSOLUTE_URI=$SERVICE_FQDN_PHPMYADMIN
    volumes:
      - 'phpmyadmin-config:/config'
    healthcheck:
      test:
        - CMD
        - curl
        - '-f'
        - 'http://127.0.0.1:80'
      interval: 2s
      timeout: 10s
      retries: 15

Container logs

2025-Aug-10 07:34:05.078183
Starting deployment of phpmyadmin:latest to OVH.
2025-Aug-10 07:34:05.244895
Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:1.0.8.
2025-Aug-10 07:34:05.344627
[CMD]: docker stop --time=30 fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:05.344627
Flag --time has been deprecated, use --timeout instead
2025-Aug-10 07:34:05.346611
Error response from daemon: No such container: fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:05.444138
[CMD]: docker rm -f fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:05.444138
Error response from daemon: No such container: fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:05.570962
[CMD]: docker run -d --network coolify --name fc4gwscggc8sgw88o4oswwg8 --rm -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/coollabsio/coolify-helper:1.0.8
2025-Aug-10 07:34:05.570962
58227bdf7da2dfd0d2850b0619b7d00472bd83fd32f0133f713d53ead9577fc6
2025-Aug-10 07:34:06.588238
----------------------------------------
2025-Aug-10 07:34:06.591410
Rolling update started.
2025-Aug-10 07:34:06.593707
Pulling latest images from the registry.
2025-Aug-10 07:34:06.845773
[CMD]: docker exec fc4gwscggc8sgw88o4oswwg8 bash -c 'docker compose --project-name p8gcgokgo84k8444s48sc0gk --project-directory /artifacts/fc4gwscggc8sgw88o4oswwg8 pull'
2025-Aug-10 07:34:06.845773
p8gcgokgo84k8444s48sc0gk-073404145542 Pulling
2025-Aug-10 07:34:06.955822
p8gcgokgo84k8444s48sc0gk-073404145542 Pulled
2025-Aug-10 07:34:07.203006
[CMD]: docker exec fc4gwscggc8sgw88o4oswwg8 bash -c ' docker compose --project-name p8gcgokgo84k8444s48sc0gk --project-directory /artifacts/fc4gwscggc8sgw88o4oswwg8 up --build -d'
2025-Aug-10 07:34:07.203006
time="2025-08-10T07:34:07Z" level=warning msg="Found orphan containers ([p8gcgokgo84k8444s48sc0gk-212250478102]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up."
2025-Aug-10 07:34:07.203006
Container p8gcgokgo84k8444s48sc0gk-073404145542  Creating
2025-Aug-10 07:34:07.234788
p8gcgokgo84k8444s48sc0gk-073404145542 Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.
2025-Aug-10 07:34:07.236733
Container p8gcgokgo84k8444s48sc0gk-073404145542  Created
2025-Aug-10 07:34:07.238031
Container p8gcgokgo84k8444s48sc0gk-073404145542  Starting
2025-Aug-10 07:34:07.411315
Container p8gcgokgo84k8444s48sc0gk-073404145542  Started
2025-Aug-10 07:34:07.424550
New container started.
2025-Aug-10 07:34:07.427294
Removing old containers.
2025-Aug-10 07:34:07.650296
[CMD]: docker stop --time=30 p8gcgokgo84k8444s48sc0gk-212250478102
2025-Aug-10 07:34:07.650296
Flag --time has been deprecated, use --timeout instead
2025-Aug-10 07:34:08.813095
p8gcgokgo84k8444s48sc0gk-212250478102
2025-Aug-10 07:34:08.977656
[CMD]: docker rm -f p8gcgokgo84k8444s48sc0gk-212250478102
2025-Aug-10 07:34:08.977656
p8gcgokgo84k8444s48sc0gk-212250478102
2025-Aug-10 07:34:08.981810
Rolling update completed.
2025-Aug-10 07:34:09.254245
Gracefully shutting down build container: fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:09.350105
[CMD]: docker stop --time=30 fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:09.350105
Flag --time has been deprecated, use --timeout instead
2025-Aug-10 07:34:09.498315
fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:09.600203
[CMD]: docker rm -f fc4gwscggc8sgw88o4oswwg8
2025-Aug-10 07:34:09.600203
Error response from daemon: No such container: fc4gwscggc8sgw88o4oswwg8

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thespad]

This works as expected on our latest image:

Setting

      - PMA_HOSTS=kimai-db,bob-db
      - PMA_VERBOSES=kimai-db,bob-db

Without PMA_ARBITRARY set.

As noted you need 2 or more entries otherwise it won't show the dropdown.

As for

Also, the VARS available from the official PMA Docker repo is significantly larger than what's available here (it's mostly SSL related but that can be pretty important). Please update this accordingly.

We specifically don't document a complete list of env vars in the readme because we can't reliably keep it up to date every time something changes upstream, which is why we link to https://docs.phpmyadmin.net/en/latest/setup.html#docker-environment-variables (also the official docker image has a few extra envs that they provide, that aren't in the official docs, with specific logic in the image to handle, and we don't necessarily support those)

[iamkevinmccarthy]

I appreciate the response. I was able to pinpoint the issue to an unexpected disconnect with Coolify's handling of vars, so it's working as expected now. I consider the initial issue resolved.

However, as for the list of vars in the readme, I wasn't referring to the readme. Specifically, if you compare the config.inc.php in your repo with the one provided by PMA, there's a significant difference in support.

Here is yours, stopping at MEMORY_LIMIT (lines 7-30):

/* Ensure we got the environment */
$vars = array(
    'PMA_ARBITRARY',
    'PMA_HOST',
    'PMA_HOSTS',
    'PMA_VERBOSE',
    'PMA_VERBOSES',
    'PMA_PORT',
    'PMA_PORTS',
    'PMA_SOCKET',
    'PMA_SOCKETS',
    'PMA_USER',
    'PMA_PASSWORD',
    'PMA_ABSOLUTE_URI',
    'PMA_CONTROLHOST',
    'PMA_CONTROLPORT',
    'PMA_PMADB',
    'PMA_CONTROLUSER',
    'PMA_CONTROLPASS',
    'PMA_QUERYHISTORYDB',
    'PMA_QUERYHISTORYMAX',
    'MAX_EXECUTION_TIME',
    'MEMORY_LIMIT'
);

Here is theirs, continuing beyond MEMORY_LIMIT (lines 6-48):

/* Ensure we got the environment */
$vars = [
    'PMA_ARBITRARY',
    'PMA_HOST',
    'PMA_HOSTS',
    'PMA_VERBOSE',
    'PMA_VERBOSES',
    'PMA_PORT',
    'PMA_PORTS',
    'PMA_SOCKET',
    'PMA_SOCKETS',
    'PMA_USER',
    'PMA_PASSWORD',
    'PMA_ABSOLUTE_URI',
    'PMA_CONTROLHOST',
    'PMA_CONTROLPORT',
    'PMA_PMADB',
    'PMA_CONTROLUSER',
    'PMA_CONTROLPASS',
    'PMA_QUERYHISTORYDB',
    'PMA_QUERYHISTORYMAX',
    'MAX_EXECUTION_TIME',
    'MEMORY_LIMIT',
    'PMA_UPLOADDIR',
    'PMA_SAVEDIR',
    'PMA_SSL',
    'PMA_SSLS',
    'PMA_SSL_DIR',
    'PMA_SSL_VERIFY',
    'PMA_SSL_VERIFIES',
    'PMA_SSL_CA',
    'PMA_SSL_CAS',
    'PMA_SSL_CA_BASE64',
    'PMA_SSL_CAS_BASE64',
    'PMA_SSL_KEY',
    'PMA_SSL_KEYS',
    'PMA_SSL_KEY_BASE64',
    'PMA_SSL_KEYS_BASE64',
    'PMA_SSL_CERT',
    'PMA_SSL_CERTS',
    'PMA_SSL_CERT_BASE64',
    'PMA_SSL_CERTS_BASE64',
];

PMA's set has more options and code to handle (mostly) various SSL parameters. Your set not only lacks the additional vars, but lacks handling of any of those should anyone want to utilize them.

For example, if someone's logging into a database that has something like require_secure_transport=ON, and there's no support in the config.inc.php file for the PMA_SSL_* vars, then they're going to have problems because even modding the Docker Compose to add the desired PMA_SSL_* vars simply won't do anything.

[thespad]

Those all look like options that have only been added in the most recent release, we'll have to look at what's changed and what's required to bring things back in line.