[root@centos vagrant]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 5979a863b844 percona/pmm-server:2 "/opt/entrypoint.sh" 55 seconds ago Up 53 seconds (unhealthy) 80/tcp, 0.0.0.0:443->443/tcp pmm-server
Add to FAQ section for users who have issue with running PMM on Centos 7 hosts. We are releasing docker images with -el7 suffix to use on Centos 7 hosts.
I agree but that is the version the customer was using.
> Can you update the docker to the latest version and check, if the problem is still accurate?
No problems with a newer version. I told the customer to upgrade as well
> We'll update the PMM doc for the minimal version recommended.
Thanks for this. I think is the right way to go because as long as we say we support an old version, customers will show up expecting the old version to work.
Deploying a new PMM 2.39 will break after setup:
[root@centos vagrant]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5979a863b844 percona/pmm-server:2 "/opt/entrypoint.sh" 55 seconds ago Up 53 seconds (unhealthy) 80/tcp, 0.0.0.0:443->443/tcp pmm-server
Steps to reproduce:
OS: CentOS 7.8
docker version:
[root@centos vagrant]# rpm -qa | grep -i docker
docker-common-1.13.1-209.git7d71120.el7.centos.x86_64
docker-1.13.1-209.git7d71120.el7.centos.x86_64
docker-client-1.13.1-209.git7d71120.el7.centos.x86_64
Follow install steps from https://docs.percona.com/percona-monitoring-and-management/setting-up/server/docker.html#run:
docker pull percona/pmm-server:2
docker volume create pmm-data
docker run --detach --restart always \ --publish 443:443 \ -v pmm-data:/srv \ --name pmm-server \ percona/pmm-server:2
If this is not a bug but an expected behaviour then the minimum docker version required should be upgraded in the documentation page: https://docs.percona.com/percona-monitoring-and-management/setting-up/server/docker.html