Skip to content
PERCONA MONITORING AND MANAGEMENT DOCUMENTATION

Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Upgrade PMM Server Docker container

Upgrade your PMM Server Docker container to the latest version, ensuring you benefit from new features, improvements, and bug fixes while preserving your monitoring data and configuration.

Important

Downgrades are not possible. To go back to using a previous version you must have created a backup of it before upgrading.

Prerequisite: check current version

Before you start upgrading, check current PMM Server version:

```sh
docker exec -it pmm-server \
curl -ku admin:admin https://localhost/v1/version
```

For remote access, replace `localhost` with your PMM Server's address.

Upgrade procedure

To upgrade the container:

  1. Stop the current PMM Server container:

    docker stop pmm-server

  2. Create a backup of your current installation:

  3. Pull the latest PMM Server image:

    docker pull percona/pmm-server:3

  4. Rename the original container to keep it as a fallback: 

    docker rename pmm-server pmm-server-old

  5. Run a new container with the latest image, connecting to your existing data. Make sure to adjust the volume parameter based on your setup (using --volumes-from for container data, --volume pmm-data:/srv for Docker volumes, or --volume /path/on/host:/srv for host directories):

    docker run \
--detach \
--restart always \
--publish 443:8443 \
--volumes-from pmm-data \
--name pmm-server \
percona/pmm-server:3

  6. Verify the upgrade was successful: 

    docker exec -it pmm-server \
curl -ku admin:admin https://localhost/v1/version

  7. Access the PMM web interface and confirm your dashboards and monitoring are working correctly.

Troubleshooting

If you encounter issues after upgrading:

  1. Check the PMM Server logs: 
    docker logs pmm-server
  2. If the upgrade fails, revert to your previous version: 
    # Stop and remove the problematic container
docker stop pmm-server
docker rm pmm-server

# Restore the backup
docker rename pmm-server-backup pmm-server
docker start pmm-server