Run Docker via the Easy-install script¶

The Easy-install script provides the simplest way to deploy PMM Server with Docker, handling all the necessary setup steps automatically.

Security best practice¶

Before running the script:

Download the installation script from the official Percona domain.
Review the script content to understand its actions.
Consider running the script with the --interactive flag to customize:
- port mappings (default: 443 for HTTPS)
- location where PMM Server stores its data
- PMM Server version (specific version or latest)
- additional configuration parameters (environment variables, resource limits)

Installation instructions¶

Linux or macOS¶

Download and install PMM Server using cURL or wget:

cURLwget

curl -fsSL https://www.percona.com/get/pmm | bash

wget -O - https://www.percona.com/get/pmm | bash

What does the script do?

This script does the following:

installs Docker if it is not already installed on your system.
stops and renames any currently running PMM Server Docker container from pmm-server to pmm-server-{timestamp}. This old pmm-server container is not a recoverable backup.
pulls and runs the latest PMM Server Docker image.
can run in Interactive mode to change the default settings:

   curl -fsSLO https://www.percona.com/get/pmm
   # or: wget https://www.percona.com/get/pmm
   chmod +x pmm
   ./pmm --interactive

Docker installation issues¶

Script fails on Rocky Linux or other unsupported distributions¶

If you encounter Docker installation issues with the Easy-install script (such as ERROR: Unsupported distribution 'rocky' on Rocky Linux):

Install Docker manually
Run the Easy-install script above again

This two-step approach resolves most installation issues, especially on Rocky Linux where automatic installation may fail.

Container keeps restarting with `/srv is not writable` error¶

If the PMM Server container keeps restarting and docker logs pmm-server shows:

FATAL: /srv is not writable for pmm user.
Make sure that /srv is owned by uid 1000 and gid 0 and try again.
You can change ownership by running: sudo chown -R 1000:0 /srv

Incorrect ownership of the PMM Docker volume typically causes this error. To fix it:

Fix ownership inside the PMM Server container:

docker exec pmm-server supervisorctl stop all
docker exec --user root pmm-server chown -R 1000:0 /srv
docker exec pmm-server supervisorctl start all

If PMM starts working, you don’t need to do anything else.

If the problem persists, stop and remove the PMM Server container:
```
docker stop pmm-server && docker rm pmm-server
```
Remove the orphaned PMM data volume:
```
docker volume rm pmm-data
```
Data loss

This permanently deletes all PMM data in the volume, including dashboards, metrics history, and configuration. Continue only if you want to start from scratch.

Run the Easy-install script again:

curl -fsSL https://www.percona.com/get/pmm | bash

If the problem persists, remove all unused Docker objects (containers, images, and networks), and try again:
```
docker system prune -a
```
To remove unused volumes as well, run:
```
docker system prune -a --volumes
```

Affects all Docker workloads

These commands remove unused Docker resources on the host, not just those related to PMM. Only run them if you are sure no other Docker workloads are affected.

Next steps¶

After PMM Server is set up successfully, set up PMM Client:

Install PMM Client