FortiClient
FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
JHelio
Staff
Staff
Article Id 407878
Description This article describes how to face the issue 'container is not running' when installing FortiClient EMS on a Linux Server.
Scope FortiClient EMS Linux 7.4 version.
Solution

During the FortiClient EMS for Linux installation process:

 

docker exec -it pg-1 bash /opt/bitnami/scripts/postgresql-repmgr/entrypoint.sh repmgr -f /opt/bitnami/repmgr/conf/repmgr.conf service status

 

When users enter the following command in the Linux server console, it results in an error:

 

docker run --restart always --detach --network ems_pg_ha --name pg-1 -p 5432:5432 \

 

The following error appears:


Error response from daemon: container XXXXXXX is not running

 

This error is because the following parameter is incorrect:

 

--network ems_pg_ha

 

Instead, the command should be as follows:

 

docker run --restart always --detach  --name pg-1 -p 5432:5432 \

 

Before re-entering the command without the incorrect parameter '--network ems_pg_ha', delete the previous attempt using the following command:

 

docker rm pg-1


Note: Always collect logs to confirm what the issue is. In this case, run 'docker logs pg-1'.