# Bitnami Secure Image for phpMyAdmin

> phpMyAdmin is a free software tool written in PHP, intended to handle the administration of MySQL over the Web. phpMyAdmin supports a wide range of operations on MySQL and MariaDB.

[Overview of phpMyAdmin](https://www.phpmyadmin.net/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

## TL;DR

```console
docker run --name phpmyadmin bitnami/phpmyadmin:latest
```

You can find the default credentials and available configuration options in the [Environment Variables](#environment-variables) section.

## Using `docker-compose.yml`

The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).

[https://github.com/bitnami/containers/tree/main/bitnami/phpmyadmin/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/phpmyadmin/docker-compose.yml)

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/phpmyadmin).

## Why use Bitnami Secure Images?

Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?

- Hardened secure images of popular open source software with Near-Zero Vulnerabilities
- Vulnerability Triage & Prioritization with VEX Statements, KEV and EPSS Scores
- Compliance focus with FIPS, STIG, and air-gap options, including secure bill of materials (SBOM)
- Software supply chain provenance attestation through in-toto
- First class support for the internet’s favorite Helm charts

Each image comes with valuable security metadata. You can view the metadata in [our public catalog here](https://app-catalog.vmware.com/bitnami/apps). Note: Some data is only available with [commercial subscriptions to BSI](https://bitnami.com/).

![Alt text](https://github.com/bitnami/containers/blob/main/BSI%20UI%201.png?raw=true "Application details")
![Alt text](https://github.com/bitnami/containers/blob/main/BSI%20UI%202.png?raw=true "Packaging report")

If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).

## How to deploy phpMyAdmin in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami phpMyAdmin Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/phpmyadmin).

## Supported tags and respective `Dockerfile` links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).

## How to use this image

phpMyAdmin requires access to a MySQL database or MariaDB database to work. We'll use the [Bitnami MariaDB image](https://github.com/bitnami/containers/tree/main/bitnami/mariadb).

### Using Docker Compose

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/phpmyadmin).

### Persisting your application

If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a volume at the `/bitnami` path. Additionally you should mount a volume for [persistence of the MariaDB data](https://github.com/bitnami/containers/blob/main/bitnami/mariadb#persisting-your-database).

To avoid inadvertent removal of these volumes you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.

## Configuration

The following section describes the supported environment variables

### Environment variables

The following tables list the main variables you can set.

#### Customizable environment variables

| Name                                   | Description                                                                                                                                            | Default Value                                  |
|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|
| `PHPMYADMIN_ALLOW_ARBITRARY_SERVER`    | Whether to enable database server hostname.                                                                                                            | `nil`                                          |
| `PHPMYADMIN_ALLOW_REMOTE_CONNECTIONS`  | Whether to allow remote connections for phpMyAdmin, or force local connections by default.                                                             | `$PHPMYADMIN_DEFAULT_ALLOW_REMOTE_CONNECTIONS` |
| `PHPMYADMIN_ABSOLUTE_URI`              | If specified, absolute URL to phpMyAdmin when generating links.                                                                                        | `nil`                                          |
| `PHPMYADMIN_EXEC_TIME_LIMIT`           | If specified, number of seconds a script is allowed to run                                                                                             | `nil`                                          |
| `PHPMYADMIN_MEMORY_LIMIT`              | If specified, number of bytes a script is allowed to allocate.                                                                                         | `nil`                                          |
| `DATABASE_HOST`                        | Database server host.                                                                                                                                  | `nil`                                          |
| `DATABASE_USER`                        | Database server user.                                                                                                                                  | `nil`                                          |
| `DATABASE_PASSWORD`                    | Database server password.                                                                                                                              | `nil`                                          |
| `DATABASE_PORT_NUMBER`                 | Database server port.                                                                                                                                  | `nil`                                          |
| `DATABASE_ALLOW_NO_PASSWORD`           | Whether to allow logins without a password.                                                                                                            | `no`                                           |
| `DATABASE_ENABLE_SSL`                  | Whether to enable SSL for the connection between phpMyAdmin and the MySQL server to secure the connection.                                             | `nil`                                          |
| `DATABASE_SSL_KEY`                     | Path to the client key file when using SSL.                                                                                                            | `${DATABASE_CERTS_DIR}/server_key.pem`         |
| `DATABASE_SSL_CERT`                    | Path to the client certificate file when using SSL.                                                                                                    | `${DATABASE_CERTS_DIR}/server_certificate.pem` |
| `DATABASE_SSL_CA`                      | Path to the CA file when using SSL.                                                                                                                    | `${DATABASE_CERTS_DIR}/ca_certificate.pem`     |
| `DATABASE_SSL_CA_PATH`                 | Directory containing trusted SSL CA certificates in PEM format.                                                                                        | `nil`                                          |
| `DATABASE_SSL_CIPHERS`                 | List of allowable ciphers for connections when using SSL.                                                                                              | `nil`                                          |
| `DATABASE_SSL_VERIFY`                  | Enable SSL certificate validation.                                                                                                                     | `yes`                                          |
| `CONFIGURATION_STORAGE_ENABLE`         | Enable phpMyAdmin configuration storage.                                                                                                               | `no`                                           |
| `CONFIGURATION_STORAGE_DB_HOST`        | phpMyAdmin configuration storage database server hostname.                                                                                             | `mariadb`                                      |
| `CONFIGURATION_STORAGE_DB_PORT_NUMBER` | phpMyAdmin configuration storage database server port.                                                                                                 | `3306`                                         |
| `CONFIGURATION_STORAGE_DB_USER`        | phpMyAdmin configuration storage database user.                                                                                                        | `pma`                                          |
| `CONFIGURATION_STORAGE_DB_PASSWORD`    | phpMyAdmin configuration storage database password.                                                                                                    | `nil`                                          |
| `CONFIGURATION_STORAGE_DB_NAME`        | phpMyAdmin configuration storage database name.                                                                                                        | `phpmyadmin`                                   |
| `CONFIGURATION_ALLOWDENY_ORDER`        | Set the AllowDeny order. If your rule order is empty, then IP authorization is disabled. Available values are: `deny,allow`, `allow,deny`, `explicit`. | `nil`                                          |
| `CONFIGURATION_ALLOWDENY_RULES`        | Array of strings to allow or deny hosts/user to connect to the database. The value must be literal, following the format `allow \                      | deny <username> [from] <ipmask>`.              |

#### Read-only environment variables

| Name                                          | Description                                                                                                                              | Value                                     |
|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|
| `PHPMYADMIN_BASE_DIR`                         | phpMyAdmin installation directory.                                                                                                       | `${BITNAMI_ROOT_DIR}/phpmyadmin`          |
| `PHPMYADMIN_VOLUME_DIR`                       | phpMyAdmin directory for mounted configuration files.                                                                                    | `${BITNAMI_VOLUME_DIR}/phpmyadmin`        |
| `PHPMYADMIN_TMP_DIR`                          | phpMyAdmin directory for temporary files.                                                                                                | `${PHPMYADMIN_BASE_DIR}/tmp`              |
| `PHPMYADMIN_CONF_FILE`                        | Configuration file for phpMyAdmin.                                                                                                       | `${PHPMYADMIN_BASE_DIR}/config.inc.php`   |
| `PHPMYADMIN_MOUNTED_CONF_FILE`                | Mounted configuration file for phpMyAdmin. It will be copied to the phpMyAdmin installation directory during the initialization process. | `${PHPMYADMIN_VOLUME_DIR}/config.inc.php` |
| `PHPMYADMIN_DEFAULT_ALLOW_ARBITRARY_SERVER`   | Whether to enable database server hostname by default.                                                                                   | `no`                                      |
| `PHPMYADMIN_DEFAULT_ALLOW_REMOTE_CONNECTIONS` | Whether to allow remote connections for phpMyAdmin, or force local connections.                                                          | `yes`                                     |
| `DATABASE_DEFAULT_HOST`                       | Default database server host.                                                                                                            | `mariadb`                                 |
| `DATABASE_DEFAULT_PORT_NUMBER`                | Default database server port.                                                                                                            | `3306`                                    |
| `DATABASE_CERTS_DIR`                          | phpMyAdmin directory for certificates.                                                                                                   | `${PHPMYADMIN_BASE_DIR}/db_certs`         |
| `PHP_DEFAULT_UPLOAD_MAX_FILESIZE`             | Default max PHP upload file size.                                                                                                        | `80M`                                     |
| `PHP_DEFAULT_POST_MAX_SIZE`                   | Default max PHP POST size.                                                                                                               | `80M`                                     |
| `PHP_DEFAULT_MEMORY_LIMIT`                    | Default PHP memory limit.                                                                                                                | `256M`                                    |

### FIPS configuration in Bitnami Secure Images

The Bitnami phpMyAdmin Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.

## Customize this image

The Bitnami phpMyAdmin Docker image is designed to be extended so it can be used as the base image for your custom web applications.

### Extend this image

Before extending this image, please note there are certain configuration settings you can modify using the original image:

- Settings that can be adapted using environment variables. For instance, you can change the ports used by Apache for HTTP and HTTPS, by setting the environment variables `APACHE_HTTP_PORT_NUMBER` and `APACHE_HTTPS_PORT_NUMBER` respectively.
- [Adding custom virtual hosts](https://github.com/bitnami/containers/blob/main/bitnami/apache#adding-custom-virtual-hosts).
- [Replacing the 'httpd.conf' file](https://github.com/bitnami/containers/blob/main/bitnami/apache#full-configuration).
- [Using custom SSL certificates](https://github.com/bitnami/containers/blob/main/bitnami/apache#using-custom-ssl-certificates).

If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below:

```Dockerfile
FROM bitnami/phpmyadmin
### Put your customizations below
...
```

## Notable Changes

### 5.0.2-debian-10-r73

- Decrease the size of the container. The configuration logic is now based on Bash scripts in the `rootfs/` folder.
- The `PHPMYADMIN_ALLOW_NO_PASSWORD` environment variable has been deprecated in favor of `DATABASE_ALLOW_NO_PASSWORD`.
- New environment variables have been added to support configuring extra PHP options: `PHP_UPLOAD_MAX_FILESIZE` for `upload_max_filesize`, and `PHP_POST_MAX_SIZE` for `post_max_size`.

### 4.8.5-debian-9-r96 and 4.8.5-ol-7-r111

- This image has been adapted so it's easier to customize. See the [Customize this image](#customize-this-image) section for more information.
- The Apache configuration volume (`/bitnami/apache`) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the Apache configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom Apache configuration files are advised to mount a volume for the configuration at `/opt/bitnami/apache/conf`, or mount specific configuration files individually.
- The PHP configuration volume (`/bitnami/php`) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the PHP configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom PHP configuration files are advised to mount a volume for the configuration at `/opt/bitnami/php/conf`, or mount specific configuration files individually.
- Enabling custom Apache certificates by placing them at `/opt/bitnami/apache/certs` has been deprecated, and support for this functionality will be dropped in the near future. Users wanting to enable custom certificates are advised to mount their certificate files on top of the preconfigured ones at `/certs`.

## License

Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

<http://www.apache.org/licenses/LICENSE-2.0>

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
