Problem running on Debian 10

[npodbielski]

I had a problem running this docker image on Debian 10. I checked this on 2 separate machines and problem was the same: image keeps restarting with error code 139. No logs. I am fairly new to docker so I had no idea what is happening. After reinstalling purging and installing it again few times I found this issue: https://github.com/docker/for-linux/issues/58 So it seems it is problem with some kernel setting. I set syscall=emulate but it suppose to be vulnerability for my server. Is this possible update docker image to run on newer CentOS?

[OhioVR]

I am also running onlyoffice on a Debian 10 machine. I have exactly the same symptoms. The mail server quits with error 139. It seems to have had some problems at roughly the same time as the OP. There isn't much to go on because I can't find any info in the logs. A long time ago I read that the mail server has to be run as a privileged container. I can't do that because I have kernel namespaces enabled and privileged is incompatible with it. However for a very long time I have been able to get it to work fine by adding the NET_ADMIN and SYS_PTRACE capabilities to my docker-compose.yml file. I tried adding ALL capabilities but to no avail.

[OhioVR]

I should mention maybe that I have kernel 4.19.0-6-amd64 I don't remember updating the kernel recently but uname -a gives out a date: 2019-11-11

[npodbielski]

Just do:

echo 'GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"'` >> /etc/default/grub update-grub reboot

In the long run it should be fixed in image, but for now I am using mailcow.

[OhioVR]

Thank you npodbielski, that helps me a lot.

[Carazyda]

Hello @npodbielski thanks for your report. In the next version we will add processing for this case, Debian 10 and the kernel 4.18+. We will also add instruction to our helpcenter.

[npodbielski]

No problem. Glad to help.

[klacointe]

Thanks!