Connection refused with docker setup

clarenze

Hi all,

I installed grommunio using docker as described in https://github.com/grommunio/gromox-container/tree/master/examples
I used the docker-compose.yaml from git. I only changed the version to "latest".

Then I started the setup using "docker compose up" and created a new user through https://localhost:8443/1/users/1.
When I press the save button, I see following error message in the console:

docker-grommunio-admin-1 | [admin] [WARNING] (flask.app) GET /api/v1/system/dashboard/services? from 172.19.0.1 -> 500 '{"message":"The server encountered an error while processing the request."}\n'

What does this mean? Why is grommunio-admin trying to contact 172.19.0.1? Isn't that the gateway?
Did I do something wrong or is this an error in the docker image?
How can I debug this? I don't even know which service is trying to access which service and where it got the idea that it could reach this via 172.19.0.1!?
Please help!

Here is the output of docker network inspect docker-grommunio_default:
[ { "Name": "docker-grommunio_default", "Id": "b847ea340ae5606608d678929192be448295dce9ecb142f2b8a566d00a81a798", "Created": "2023-12-26T10:48:16.529227769+01:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": true, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.19.0.0/16", "Gateway": "172.19.0.1" }, { "Subnet": "fd12:3456:789a:1::/64", "Gateway": "fd12:3456:789a:1::1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "4fdd21a0c37b52fa960717c5e209c647da10f276c18bfbee2819f5d320e51f4e": { "Name": "docker-grommunio-core-1", "EndpointID": "240c175a85e75fa4605fe2d13f331c67e0d6dc496e0f1fa940994a6d92820c8d", "MacAddress": "02:42:ac:13:00:03", "IPv4Address": "172.19.0.3/16", "IPv6Address": "fd12:3456:789a:1::3/64" }, "79b3c6c5ab634b650c1042a8b96ad8326c9f7e5d3c4761149366cb244cb78ae8": { "Name": "docker-grommunio-db-1", "EndpointID": "ea1f99ad0c8f7ad2299edd5d24f7bae09380d211e50f17f540814889e971ff04", "MacAddress": "02:42:ac:13:00:02", "IPv4Address": "172.19.0.2/16", "IPv6Address": "fd12:3456:789a:1::2/64" }, "880731ab0e5e25882240e76f351d4dc6cde17065ed3d519e30c26279389b9cdf": { "Name": "docker-grommunio-admin-1", "EndpointID": "a2d0711b892d8c3a027ad9b685e382824d0f6e79516139e6e4885aa90a69a57f", "MacAddress": "02:42:ac:13:00:04", "IPv4Address": "172.19.0.4/16", "IPv6Address": "fd12:3456:789a:1::4/64" } }, "Options": {}, "Labels": { "com.docker.compose.network": "default", "com.docker.compose.project": "docker-grommunio", "com.docker.compose.version": "2.21.0" } } ]

I am using the docker-ce package version 5:24.0.7-1_debian.11_bullseye.
Here are the service versions:
for i in docker-grommunio-admin-1 docker-grommunio-core-1 docker-grommunio-db-1; do echo $i; docker inspect $i | grep -i version; done docker-grommunio-admin-1 "com.docker.compose.version": "2.21.0", "org.opencontainers.image.version": "15.5.5.4", "org.opensuse.base.version": "15.5.5.4", docker-grommunio-core-1 "com.docker.compose.version": "2.21.0", "org.opencontainers.image.version": "15.5.5.4", "org.opensuse.base.version": "15.5.5.4", docker-grommunio-db-1 "GOSU_VERSION=1.17", "MARIADB_VERSION=1:10.11.6+maria~ubu2204" "com.docker.compose.version": "2.21.0", "org.opencontainers.image.version": "10.11.6"

clarenze

I still was not able to find the root cause of this. I suppose the docker image is broken.

Unaware3014

I had the same problems. For me it also seems the docker image is not working proberly. I switched to a VM and installed the appliance. It feels much better and smoother.

fmorettini

In https://community.grommunio.com/d/1268-docker-installation/5 someone from Grommunio already said that the current container does not work and needs redevelopment.