-
Notifications
You must be signed in to change notification settings - Fork 68
Container not reachable on port 9980 after startup, weird defunct lo_startmain processes in process list #3
Comments
Any updates on this? I have almost the same problem, except I don't have any warnings about low disk space in my docker logs.
Docker Logs:
|
I'm on the same team as @Jonast . And I tried the new version of CODE 2.1 today on the same machine he used. Now we have only a few defunct processes left:
On another machine where code is working, I only have one defunct process:
Maybe I should mention that the docker-compose file I use on the other machine looks very much the same. The only differences I could imagine have an effect on the problem are, that one is running kernel 3.16 (code is working) and one is running 4.9 (code is NOT working) Both are on debian stable. |
same issue: cant reach by all methods.
here is my docker-compose.yml
Docker logs
|
@timar any idea on what is happening here? This makes it impossible to run collabora on the affected linux systems |
+1 if i try to access to the admin console, i've got the basic auth username/password form but it's looping. host: debian stretch docker run -t -d --name collabora -p 127.0.0.1:9980:9980 -e 'domain=subdomain\.domain\.tld' --network=mynetwork --cap-add MKNOD -e "username=user" -e "password=password" collabora/code:2.1.5 docker logs collabora
docker exec collabora ps -eaf
I would appreciate any information/workaround/update |
Please try this:
Until you see this message:
Example output:
|
Same problem here on Debian bullseye. Any solution to this? |
I just tried running a container based on collabora/code which I plan to use with nextcloud. However, currently the container launches but I cannot reach it on port 9980 in any way (I tried directly connecting to the container's local ip on port 9980 to no avail) and when I open up a shell in the container, I have a huge list of weird defunct processes:
This is the docker log of the container:
The text was updated successfully, but these errors were encountered: