OCIS Startup Issue - Docker Swarm / Portainer

[bitbytenybble110]

I am attempting to host OCIS 7.0 with Collabora/Tika/ClamAV from Docker Swarm using Portainer.

Deploying the stack using the attached docker compose file is successful.

After starting the stack opening the OCIS URL reports that the configuration is missing or invalid.

Checking the OCIS container log reveals that there was an error registering the app provider:

ERR runtime/asm_amd64.s:1695 > error registering app provider: error calling add app provider | pid=1 error=rpc error: code = Unavailable desc = last connection error: connection error: desc = "transport: Error while dialing: dial tcp 10.0.0.198:9142: i/o timeout"

Attempting to open a socket connection to the GRPC gateway fails with a timeout error.

Running lsof -i -P -n | grep LISTEN | grep 9142 on the Docker host shows that the port is listening. Stopping the OCIS stack closes the port on the host so there does not appear to be a host port conflict.

The problem however is intermittent. Restarting the OCIS stack repeatedly will occasionally allow connections to the GRPC gateway.

Changing the binding port of the GRPC gateway does not resolve the issue.

Changing GATEWAY_GRPC_ADDR format to :9142 instead of 0.0.0.0:9142 does not resolve the issue.

Commenting out the GATEWAY_GRPC_ADDR entry in the compose file allows OCIS to start normally and allow logins but breaks collaboration integration.

We have completely deleted our OCIS stack, configuration files and data and redeployed with a fresh instance but the problem persists.

This problem has been seen in OCIS 5, 6, and 7 across multiple Docker versions.

Steps to reproduce

1. Deploy OCIS using the attached docker compose file.
2. Start the OCIS stack

Expected behavior

The GRPC gateway should bind to the port listed in the docker compose file, start, and respond consistently.

Actual behavior

The GRPC gateway binds to the port listed in the docker compose file but does not always respond to connections.

Setup

OCIS version 7.0.0
Portainer version 2.21.6
Docker version 27.4.1
Docker compose file: OCIS-COMPOSE.txt

[bitbytenybble110]

Writing to report that this problem seems to be related to Docker Swarms overlay networks.

This problem is not reproducible if the OCIS instance is started using docker compose up instead of Portainer in Docker Swarm mode.