Closed cmeessen closed 8 months ago
I cannot reproduce this, making it hard for me to debug, although I've also seen this on someone else's VM.
Some suggestions to try to find out what coponent causes the bug:
authentication/pom.xml
authentication/Dockerfile
If someone who experiences this bug can give me root access to a (toy) VM, I can maybe look into it further.
One idea is to change the Auth service to open a ServerSocket manually to see if the same bug happens when sending TCP requests to the container.
We currently experience problems with the auth container on our staging server. The container does not accept connections after about 60s without connection attempts. The problem first occurred when testing v2.1.1 after the docker version on the server was updated. This is a list of packages on our staging server that, when upgraded, will result in the bug:
Some more observations
As the problem occurs with v2.1.1, it appears that it's related to the combination of docker version and the upgraded Java version inside the auth container.
We could not yet discover a proper solution, but adding a healthcheck to the auth container keeps it alive:
It checks every 10s whether the container accepts connections, and if not will kill the java process. Docker will then restart the container according to the restart policy.