Running dhis2 on docker using an existing database

KMurumba · 22 September 2021 10:36

Hi,
Anyone here who has been able to run dhis2 on docker using an already existing Postgres database that is also running on docker? Will gladly appreciate your assistance.

Note: I’m trying to run dhis2 instance on docker on the Apple M1 laptop which I am unable to. I used these instructions to prepare my yml file

Thanks.

Gassim · 22 September 2021 12:49

Hey thanks for sharing the guide that you used, may I ask why are you not able to? Do you see any errors?

Please review this page: https://developers.dhis2.org/docs/#installing-prerequisites, you’d be using the “If you are using OSX or Windows” instructions.

jaime.bosque · 23 September 2021 07:56

Hi @KMurumba . If you are using a yaml file I am assuming you are using docker-compose in order to launch the different docker containers. Is the postgresql container included in the definition? If that’s not the case you might not be able to communicate because docker will block connections between containers unless open explicitly. Also, if you are trying to resolve a dns name (like in the example db) and the container is not defined the substitution of that name-ip will not be make and therefore the connection will fail.

In any case, your best start should be, as @Gassim is mentioning, check for the logs to see what errors you are getting.

KMurumba · 23 September 2021 08:40

Hey @jaime.bosque I have tried the option stated by @Gassim and I am getting 502 Bad Gateway when I try to access http:localhost:8080

Below are the error logs when I tail the instance:

dockergen.1 | 2021/09/23 08:45:57 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
dockergen.1 | 2021/09/23 08:45:57 Running 'nginx -s reload'
dockergen.1 | 2021/09/23 08:45:57 Watching docker events
dockergen.1 | 2021/09/23 08:45:57 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
2021/09/23 08:46:00 [notice] 47#47: signal process started
dhparam generation complete, reloading nginx
nginx.1     | 2021/09/23 08:46:22 [error] 49#49: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.26.0.3:8080/dhis-web-dashboard", host: "localhost:8080"
nginx.1     | 2021/09/23 08:46:22 [error] 49#49: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.26.0.3:8080/favicon.ico", host: "localhost:8080", referrer: "http://localhost:8080/dhis-web-dashboard"
nginx.1     | 2021/09/23 08:47:38 [error] 49#49: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.26.0.3:8080/dhis-web-dashboard", host: "localhost:8080"
nginx.1     | 2021/09/23 08:47:38 [error] 49#49: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.26.0.3:8080/favicon.ico", host: "localhost:8080", referrer: "http://localhost:8080/dhis-web-dashboard"
nginx.1     | 2021/09/23 08:47:39 [error] 49#49: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.26.0.3:8080/dhis-web-dashboard", host: "localhost:8080"
nginx.1     | 2021/09/23 08:47:39 [error] 49#49: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.26.0.3:8080/favicon.ico", host: "localhost:8080", referrer: "http://localhost:8080/dhis-web-dashboard"
nginx.1     | 2021/09/23 08:47:49 [error] 49#49: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.26.0.3:8080/dhis-web-dashboard", host: "localhost:8080"
nginx.1     | 2021/09/23 08:47:49 [error] 49#49: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 172.26.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.26.0.3:8080/favicon.ico", host: "localhost:8080", referrer: "http://localhost:8080/dhis-web-dashboard"

Gassim · 23 September 2021 08:58

Hey, did you make sure that you have installed all the prerequisites properly as the doc? Please, what do you see when you use: d2 cluster list do you see the instance you are trying to spin up? Thanks!

@KMurumba, @jaime.bosque is right you are using “docker-compose” so if you want to follow the guide I sent you, you’ll have to use Docker Desktop. If you really need to use docker-compose then I’d say continue using the guide you are already using, and please:

KMurumba · 23 September 2021 09:08

Yes @Gassim I am seeing the instance available.
│ 2.35.0 │ 8080 │ stable │ 2.35.0 │ 2.35 │ Up 8 minutes │

KMurumba · 23 September 2021 09:14

Should this be the default url http://localhost:8080/dhis-web-dashboard ? @Gassim Anything I am missing to get the 502 error?

austin · 23 September 2021 09:27

@KMurumba can you please share exactly the command you used to create this cluster? I assume it was something like this:

d2 cluster up 2.35.0 --port 8080 --dhis2-version 2.35.0 --db-version 2.35 --seed

However, as you are trying to connect to a separate Postgres database container you should not need the db-version or the seed (from you d2 cluster list output it appears you passed at least a db-version). How are you overriding the docker-compose yml file? There are ways to do this, and also ways to tell the dhis2 instance to connect to an external database, but they are not the intended use of d2 cluster. If you simply want to seed the database from a .sql file you can do so by passing --seed-file mydb.sql.gz instead of --db-version 2.35.

Finally, to debug the error you are seeing you should look at the logs of the DHIS2 container, not the nginx gateway container. You cad do this in d2 cluster with the command d2 cluster logs 2.35.0 core.

Gassim · 23 September 2021 09:30

I’d make sure to follow Austin’s post word for word!

Also, just a random thought, did you try to use a different port number?

d2 cluster down 2.35.0

Then when running it up, enter the command with another port number:

d2 cluster up 2.35.0 --port 8083

KMurumba · 23 September 2021 09:36

So I dropped the docker-compose way and fully setting us using the dhis cli. I have run the exact commands above but I am still getting 502 Bad Gateway error. I would like to use the cli fully for both the database and the instance.

austin · 23 September 2021 09:39

@KMurumba can you share exactly the command you used to originally set up the cluster? The command @Gassim shared only works if a cluster named 2.35.0 has already been set up and configured. You can clear the existing cluster completely and start “fresh” by running d2 cluster down --clean 2.35.0 then the full d2 cluster up command specifying the configuration you want.

When you receive a 502 Bad Gateway error, please share the output of the d2 cluster logs 2.35.0 core command which will show any errors thrown by the DHIS2 core instance

KMurumba · 23 September 2021 09:46

Hey @austin I ran this command: d2 cluster up 2.35.0 --port 8083 --dhis2-version 2.35.0 --db-version 2.35 --seed
This is after running: d2 cluster down --clean 2.35.0

Below are the error logs when i run d2 cluster logs 2.35.0 core

core_1     |   inflating: /usr/local/tomcat/webapps/ROOT/dhis-web-sms-configuration/favicon.ico  
 core_1     |   inflating: /usr/local/tomcat/webapps/ROOT/dhis-web-sms-configuration/service-worker.js  
core_1     |   inflating: /usr/local/tomcat/webapps/ROOT/dhis-web-sms-configuration/favicon-48x48.png  
 core_1     |   inflating: /usr/local/tomcat/webapps/ROOT/dhis-web-sms-configuration/manifest.webapp  
 core_1     |   inflating: /usr/local/tomcat/webapps/ROOT/META-INF/maven/org.hisp.dhis/dhis-web-portal/pom.xml  
 core_1     |   inflating: /usr/local/tomcat/webapps/ROOT/META-INF/maven/org.hisp.dhis/dhis-web-portal/pom.properties  
 core_1     | 23-Sep-2021 09:33:26.855 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/8.5.50
core_1     | 23-Sep-2021 09:33:26.867 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Dec 7 2019 19:19:46 UTC
 core_1     | 23-Sep-2021 09:33:26.867 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 8.5.50.0
 core_1     | 23-Sep-2021 09:33:26.868 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
 core_1     | 23-Sep-2021 09:33:26.868 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            5.10.47-linuxkit
 core_1     | 23-Sep-2021 09:33:26.868 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
core_1     | 23-Sep-2021 09:33:26.869 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/local/openjdk-8/jre
 core_1     | 23-Sep-2021 09:33:26.870 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_242-b08
 core_1     | 23-Sep-2021 09:33:26.870 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
 core_1     | 23-Sep-2021 09:33:26.870 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /usr/local/tomcat
 core_1     | 23-Sep-2021 09:33:26.871 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /usr/local/tomcat
 core_1     | 23-Sep-2021 09:33:26.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properties
core_1     | 23-Sep-2021 09:33:26.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
 core_1     | 23-Sep-2021 09:33:26.873 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
core_1     | 23-Sep-2021 09:33:26.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
 core_1     | 23-Sep-2021 09:33:26.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
 core_1     | 23-Sep-2021 09:33:26.874 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcontext.path=
core_1     | 23-Sep-2021 09:33:26.875 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
 core_1     | 23-Sep-2021 09:33:26.875 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/usr/local/tomcat
 core_1     | 23-Sep-2021 09:33:26.876 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/usr/local/tomcat
 core_1     | 23-Sep-2021 09:33:26.876 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/usr/local/tomcat/temp
 core_1     | 23-Sep-2021 09:33:26.876 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.6.5].
 core_1     | 23-Sep-2021 09:33:26.877 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
 core_1     | 23-Sep-2021 09:33:26.877 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
 core_1     | 23-Sep-2021 09:33:26.902 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1d  10 Sep 2019]
 core_1     | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
 gateway_1  | nginx.1     | 2021/09/23 09:34:46 [error] 46#46: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:34:47 [error] 46#46: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 db_1       | 2021-09-23 09:35:01.114 UTC [129] PANIC:  stuck spinlock detected at LWLockWaitListLock, lwlock.c:821
db_1       | 2021-09-23 09:35:01.114 UTC [129] STATEMENT:  CREATE EXTENSION IF NOT EXISTS postgis_tiger_geocoder;
db_1       | qemu: uncaught target signal 6 (Aborted) - core dumped
 db_1       | PANIC:  stuck spinlock detected at LWLockWaitListLock, lwlock.c:821
 db_1       | server closed the connection unexpectedly
db_1       | 	This probably means the server terminated abnormally
db_1       | 	before or while processing the request.
db_1       | 2021-09-23 09:35:01.164 UTC [91] LOG:  server process (PID 129) was terminated by signal 6
db_1       | 2021-09-23 09:35:01.164 UTC [91] DETAIL:  Failed process was running: CREATE EXTENSION IF NOT EXISTS postgis_tiger_geocoder;
db_1       | 2021-09-23 09:35:01.165 UTC [91] LOG:  terminating any other active server processes
db_1       | connection to server was lost
 db_1       | 2021-09-23 09:35:01.168 UTC [103] WARNING:  terminating connection because of crash of another server process
 db_1       | 2021-09-23 09:35:01.168 UTC [103] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
db_1       | 2021-09-23 09:35:01.168 UTC [103] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
 gateway_1  | dockergen.1 | 2021/09/23 09:35:01 Received event die for container 4f89f790e594
 gateway_1  | dockergen.1 | 2021/09/23 09:35:01 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
 gateway_1  | dockergen.1 | 2021/09/23 09:35:01 Received event start for container 4f89f790e594
 gateway_1  | dockergen.1 | 2021/09/23 09:35:01 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
 db_1       | 2021-09-23 09:35:01.804 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
 db_1       | 2021-09-23 09:35:01.804 UTC [1] LOG:  listening on IPv6 address "::", port 5432
 db_1       | 2021-09-23 09:35:01.807 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
 db_1       | 2021-09-23 09:35:01.846 UTC [50] LOG:  database system was interrupted; last known up at 2021-09-23 09:32:37 UTC
 db_1       | 2021-09-23 09:35:02.061 UTC [50] LOG:  database system was not properly shut down; automatic recovery in progress
 db_1       | 2021-09-23 09:35:02.063 UTC [50] LOG:  redo starts at 0/1638358
 db_1       | 2021-09-23 09:35:02.810 UTC [50] LOG:  invalid record length at 0/2E38B20: wanted 24, got 0
 db_1       | 2021-09-23 09:35:02.810 UTC [50] LOG:  redo done at 0/2E38AE8
 db_1       | 2021-09-23 09:35:02.810 UTC [50] LOG:  last completed transaction was at log time 2021-09-23 09:32:44.093014+00
 db_1       | 2021-09-23 09:35:02.930 UTC [1] LOG:  database system is ready to accept connections
 gateway_1  | nginx.1     | 2021/09/23 09:37:46 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:46 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:47 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:47 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:48 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:48 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:48 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:48 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:48 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:49 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:50 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:50 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:50 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 gateway_1  | nginx.1     | 2021/09/23 09:37:50 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /dhis-web-dashboard HTTP/1.1", upstream: "http://172.30.0.3:8080/dhis-web-dashboard", host: "localhost:8083"
 gateway_1  | nginx.1     | 2021/09/23 09:37:50 [error] 46#46: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.0.1, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.30.0.3:8080/favicon.ico", host: "localhost:8083", referrer: "http://localhost:8083/dhis-web-dashboard"
 ^C

KMurumba · 27 September 2021 06:47

Hey @austin any updates on this? @Gassim @jaime.bosque

Thanks.

austin · 27 September 2021 08:37

Hi @KMurumba - as you can see the core has a segmentation fault on startup. A few questions which might help track down the issue:

Have you tried with the latest 2.35 patch? 2.35.8-embargoed is due out soon, but in the meantime I would recommend 2.35.7-embargoed
Which versions of Docker and Docker-Compose are you running?
How much memory does your system have and how much has been allocated to Docker?

austin · 27 September 2021 11:00

This could be related to running on Apple silicone… I think others have used d2 cluster on M1 macbooks in the past, but they will have to comment here.

dancocos · 27 September 2021 20:35

Here at BAO we’ve been developing a Docker image, we initially were using it for our internal teams, it allows an existing Postgres db. We’ve tested it on M1 Macs, Intel Macs, Linux and Windows 10. You can find the repo here GitHub - baosystems/docker-dhis2: DHIS2 on Tomcat

alanivey · 1 October 2021 13:42

If you only need to run DHIS2 on your workstation, you can rebuild PostgreSQL 13 + PostGIS 3.1 into your local Docker installation using the following:

docker buildx build \
  --pull \
  --file 14-3.2/Dockerfile \
  --tag postgis:latest \
  --tag postgis:14-3.2 \
  --load \
  github.com/postgis/docker-postgis#master

If you don’t want to do that, I’ve been pushing an updated image for this to the GHCR every week or so; you can use the image via docker pull ghcr.io/baosystems/postgis:14-3.2

EDIT (2021-10-22): We are now rebuilding multiple versions of PostgreSQL with PostGIS as a multi-arch image for amd64 and arm64. It is scheduled to build weekly, one day after the official amd64-only image is built and pushed to Docker Hub. You can see available tags and the GHA job spec.