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 407879
Description This article describes the solution when the error: 'Error response from daemon: , wait until the container is running' appears during the EMS installation process in a Linux server. 
Scope FortiClient EMS Linux server installation 7.4 version. 
Solution

During the installation process, according to below installation guide link:

Installing EMS HA with Postgres HA using Bitnami Docker

 

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

 

It can show the following error message:


Error response from daemon: Container XXXXX is restarting, wait until the container is running

 

Error is due pg-1 and pg-2 nodes wrong values for:  REPMGR_PRIMARY_HOST, REPMGR_PARTNER_NODES, REPMGR_NODE_NAME y REPMGR_NODE_NETWORK_NAME

 

Set correct values according to the IP address of each pg-1/pg-2 node, for example: 

 

docker run --restart always --detach --name pg-1 -p 5432:5432 \
--env POSTGRESQL_PASSWORD=postgres \
--env POSTGRESQL_DAEMON_USER=postgres \
--env REPMGR_PASSWORD=postgres \
--env REPMGR_PRIMARY_HOST=X.X.X.X \  <----------
--env REPMGR_PRIMARY_PORT=5432 \
--env REPMGR_PARTNER_NODES=X.X.X.X,Y.Y.Y.Y:5432 \ <-----------
--env REPMGR_NODE_NAME=pg-1 \
--env REPMGR_NODE_NETWORK_NAME=X.X.X.X \ <---------
--env REPMGR_PORT_NUMBER=5432 \
--volume pg_1_data:/bitnami/postgresql \
-it \
ems-postgres-ha

 

Where X.X.X.X and Y.Y.Y.Y belong to each pg-1/pg-2 node values.