# Restarting Docker results in "Failed to fork child processes"

**URL:** <https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209>\
**Category:** 📄 Office\
**Tags:** collabora-online\
**Created:** [May 5, 2017, 12:27pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209 "2017-05-05T12:27:54Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 5, 2017, 12:27pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/1 "2017-05-05T12:27:54Z")

</div>

I’ve just updatet collabora (after [this news](https://nextcloud.com/blog/collabora-online-2.1-is-out-with-great-improvements/) post appeard). When I’m restarting the docker and do a docker logs -f on the newly created instance, I’m getting the error messages

> Signature ok  
> subject=/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost  
> Getting CA Private Key  
> loolforkit version details: 2.1.0 - b2e736a3  
> wsd-00024-00024 12:19:17.366557 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2405  
> Failed to fork child processes.  
> wsd-00024-00024 12:19:17.448691 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2551  
> Failed to fork child processes.  
> wsd-00024-00024 12:19:17.454898 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445  
> wsd-00024-00024 12:19:17.455120 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.539647 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.539732 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.539758 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.539783 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.539806 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.539827 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.540641 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 12:19:17.540684 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> frk-00026-00026 12:19:18.555660 [forkit] FTL Pipe closed.| common/IoUtil.cpp:309

Any advice on how to solve this? This worked fine with the previous (2.0) releases of Collabora docker, only after updating to 2.1 this started appearing. Server itself is unchanged.

---

<div class="post-metadata">

**Author:** ![simonj](https://help.nextcloud.com/letter_avatar/simonj/32/5_5575768a8748004e209b776fc1b2916d.png) [@simonj](https://help.nextcloud.com/u/simonj)\
**Post date:** [May 5, 2017, 3:52pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/2 "2017-05-05T15:52:28Z")

</div>

Very similar error for me:

> Generating RSA private key, 2048 bit long modulus  
> …+++  
> …+++  
> e is 65537 (0x10001)  
> Generating RSA private key, 2048 bit long modulus  
> …+++  
> …+++  
> e is 65537 (0x10001)  
> Signature ok  
> subject=/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost  
> Getting CA Private Key  
> loolforkit version details: 2.1.0 - b2e736a3  
> kit-00030-00028 15:44:46.232637 [loolkit] ERR symlink(“…/lo”,“/opt/lool/child-roots/30/opt/collaboraoffice5.3”) failed (errno: File exists)| kit/Kit.cpp:271  
> kit-00030-00028 15:44:46.233054 [loolkit] ERR Poco Exception: Exception: symlink() failed| kit/Kit.cpp:1895  
> wsd-00026-00026 15:45:35.412317 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2405  
> Failed to fork child processes.  
> wsd-00026-00026 15:45:35.413349 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2551  
> Failed to fork child processes.  
> wsd-00026-00026 15:45:35.413943 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445  
> wsd-00026-00026 15:45:35.414003 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.414765 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.414809 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.414825 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.414850 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.414864 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.414876 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.415178 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00026 15:45:35.415209 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> frk-00028-00028 15:45:35.420734 [forkit] FTL Pipe closed.| common/IoUtil.cpp:309  
> Generating RSA private key, 2048 bit long modulus  
> …+++  
> …+++  
> e is 65537 (0x10001)  
> Generating RSA private key, 2048 bit long modulus  
> …+++  
> …+++  
> e is 65537 (0x10001)  
> Signature ok  
> subject=/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost  
> Getting CA Private Key  
> loolforkit version details: 2.1.0 - b2e736a3  
> office version details: { “ProductName”: “Collabora Office”, “ProductVersion”: “5.3”, “ProductExtension”: “.10.10”, “BuildId”: “77b0d93c0f6ff6490e909dbd81b1994862a31b3a” }  
> wsd-00025-00026 15:46:05.788348 [prisoner\_poll] WRN ForKit not responsive for 24823 ms forking 1 children. Resetting.| wsd/LOOLWSD.cpp:338  
> kit-00032-00027 15:46:05.872950 [loolkit] ERR symlink(“…/lo”,“/opt/lool/child-roots/32/opt/collaboraoffice5.3”) failed (errno: File exists)| kit/Kit.cpp:271  
> kit-00032-00027 15:46:05.900306 [loolkit] ERR Poco Exception: Exception: symlink() failed| kit/Kit.cpp:1895

---

<div class="post-metadata">

**Author:** ![victorbw](https://help.nextcloud.com/letter_avatar/victorbw/32/5_5575768a8748004e209b776fc1b2916d.png) [@victorbw](https://help.nextcloud.com/u/victorbw)\
**Post date:** [May 8, 2017, 10:38am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/3 "2017-05-08T10:38:18Z")

</div>

same here!

---

<div class="post-metadata">

**Author:** ![pieter](https://help.nextcloud.com/letter_avatar/pieter/32/5_5575768a8748004e209b776fc1b2916d.png) [@pieter](https://help.nextcloud.com/u/pieter)\
**Post date:** [May 8, 2017, 12:48pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/4 "2017-05-08T12:48:35Z")

</div>

Upgrading to CODE 2.1 leaves me with a collabora/code instance that restarts about every 30 to 60 seconds. It sort of cannot really start properly and retries continuously.

I reverted back to 2.0

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 9, 2017, 11:47am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/5 "2017-05-09T11:47:00Z")

</div>

I’ve just updated my docker-engine (17.05.0~ce-0~ubuntu-xenial) but I’m still getting the same issue.

For anyone else having this: be adviced that (at least in my case) the restarts (that “pieter” mentions above) are happeing for me as well and they fill up my hard disk. I have to **docker stop ID** and (just for the sake of it) **docker rm ID**

---

<div class="post-metadata">

**Author:** ![maxidor](https://help.nextcloud.com/letter_avatar/maxidor/32/5_5575768a8748004e209b776fc1b2916d.png) [@maxidor](https://help.nextcloud.com/u/maxidor)\
**Post date:** [May 15, 2017, 12:41pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/6 "2017-05-15T12:41:36Z")

</div>

Also having the same issue - any feedback from devs?

My personal log:

```
Generating RSA private key, 2048 bit long modulus
................................................+++
....................................................+++
e is 65537 (0x10001)
Generating RSA private key, 2048 bit long modulus
...........................................................................+++
..................+++
e is 65537 (0x10001)
Signature ok
subject=/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost
Getting CA Private Key
loolforkit version details: 2.1.0 - b2e736a3
frk-00028-00028 12:43:06.022633 [forkit] FTL Capability cap_sys_chroot is not set for the loolforkit program.| kit/ForKit.cpp:151
frk-00028-00028 12:43:06.022670 [forkit] FTL Capability cap_mknod is not set for the loolforkit program.| kit/ForKit.cpp:151
frk-00028-00028 12:43:06.022701 [forkit] FTL Capability cap_fowner is not set for the loolforkit program.| kit/ForKit.cpp:151
wsd-00026-00026 12:43:56.018650 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2405
Failed to fork child processes.
wsd-00026-00026 12:43:56.018794 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2551
Failed to fork child processes.
wsd-00026-00026 12:43:56.018885 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445
wsd-00026-00026 12:43:56.018904 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019084 [loolwsd] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019097 [loolwsd] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019103 [loolwsd] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019109 [loolwsd] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019114 [loolwsd] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019119 [loolwsd] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019211 [loolwsd] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:445
<shutdown>-00026 12:43:56.019222 [loolwsd] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:445
```

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 15, 2017, 12:45pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/7 "2017-05-15T12:45:16Z")

</div>

Sorry, I haven’t found any soltion to this so far, I’ve tried to investigate myself (on the source code) but I really don’t know what’s going on there (C++ is not my strongest side…).  
I’ve also tried to get some help from people in IRC chats but so far, unfortunately, no one could help.

If I figure anything out, I’ll make sure to share my solution.

---

<div class="post-metadata">

**Author:** ![Eneas](https://help.nextcloud.com/letter_avatar/eneas/32/5_5575768a8748004e209b776fc1b2916d.png) [@Eneas](https://help.nextcloud.com/u/Eneas)\
**Post date:** [May 16, 2017, 8:16pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/8 "2017-05-16T20:16:18Z")

</div>

The same here. I also get this error message. My configuration can be found here: [Permission denied](https://help.nextcloud.com/t/permission-denied/12669)

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 17, 2017, 7:04am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/9 "2017-05-17T07:04:18Z")

</div>

Still no luck, just documenting my trials and unsuccessful attempts:

After reading [Permission denied - #2 by myshevchuk](https://help.nextcloud.com/t/permission-denied/12669/2) (Answer to Eneas thread) I thought I might have a conflicting docker / kernel issue as well:

I checked my installed docker (on Ubuntu), it was docker-engine:

> apt list --installed | grep docker  
> docker --version  
> Docker version 17.05.0-ce, build 89658be)

Then I instaled [docker.io](http://docker.io) instead (see [1] for differences)

> apt purge docker-engine; apt install [docker.io](http://docker.io)  
> docker --version  
> Docker version 1.12.6, build 78d1802

However, the error remains exactly the same:

[details=docker -l debug logs -f DOCKER\_ID]\> Generating RSA private key, 2048 bit long modulus

> …+++  
> …+++  
> e is 65537 (0x10001)  
> Signature ok  
> subject=/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost  
> Getting CA Private Key  
> loolforkit version details: 2.1.0 - b2e736a3  
> wsd-00024-00024 06:54:08.272296 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2405  
> Failed to fork child processes.  
> wsd-00024-00024 06:54:08.274339 [loolwsd] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2551  
> Failed to fork child processes.  
> wsd-00024-00024 06:54:08.278844 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445  
> wsd-00024-00024 06:54:08.279161 [loolwsd] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.283357 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.283444 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.283526 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.283566 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.283630 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.283705 [loolwsd] WRN Waking up dead poll thread [accept\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.284083 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> -00024 06:54:08.284149 [loolwsd] WRN Waking up dead poll thread [websrv\_poll], started: false, finished: false| ./net/Socket.hpp:445  
> frk-00026-00026 06:54:08.289767 [forkit] FTL Pipe closed.| common/IoUtil.cpp:309[/details]

So I’m still not able to run collabora/code docker, unfortunately.

[1] [https://www.quora.com/What-is-the-difference-between-docker-engine-and-docker-io-packages](https://www.quora.com/What-is-the-difference-between-docker-engine-and-docker-io-packages)

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 19, 2017, 10:37am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/10 "2017-05-19T10:37:38Z")

</div>

Next unsuccessful attempt: I’ve increased the RAM for my virtual machine (which is running collaborad docker container) to 4 GB (was: 1 GB) - still the same error message.

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 24, 2017, 1:18pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/11 "2017-05-24T13:18:51Z")

</div>

Cross-posted to

> <https://github.com/CollaboraOnline/Docker-CODE/issues/10>

Though that issues tracker seems close to dead (10 issues? 1 contributor to repository?)

---

<div class="post-metadata">

**Author:** ![schweidj](https://help.nextcloud.com/letter_avatar/schweidj/32/5_5575768a8748004e209b776fc1b2916d.png) [@schweidj](https://help.nextcloud.com/u/schweidj)\
**Post date:** [May 26, 2017, 9:13am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/12 "2017-05-26T09:13:59Z")

</div>

Same problem here.  
Is there a possibility to pull image v2.0 of collabora/code instead of the latest? I tried several tags with the pull command with no luck.

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 30, 2017, 12:15pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/13 "2017-05-30T12:15:10Z")

</div>

> [@schweidj](#):
>
> Is there a possibility to pull image v2.0 of collabora/code instead of the latest?

I don’t think this is possible, I’ve not seen any “older” tag being available.

I’m asking on IRC as well about this topic, but unfortunately, no solution as of now that I know of.

---

<div class="post-metadata">

**Author:** ![g.grosskopf](https://help.nextcloud.com/letter_avatar/g.grosskopf/32/5_5575768a8748004e209b776fc1b2916d.png) [@g.grosskopf](https://help.nextcloud.com/u/g.grosskopf)\
**Post date:** [May 31, 2017, 7:33am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/14 "2017-05-31T07:33:56Z")

</div>

i got the same problem, it’s not exactly docker-specific, i got it outside of docker as well, version 2.1.1 here 😕 if there is anything to try, any certain logs that might help, i can paste them here

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 31, 2017, 7:56am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/15 "2017-05-31T07:56:24Z")

</div>

Funny, I’ve just run “docker pull” again, it now works again. I’ve not changed anything in my set-up nor the way I run the docker.

For me, this issue seems to be fixed with the newest docker image…

---

<div class="post-metadata">

**Author:** ![g.grosskopf](https://help.nextcloud.com/letter_avatar/g.grosskopf/32/5_5575768a8748004e209b776fc1b2916d.png) [@g.grosskopf](https://help.nextcloud.com/u/g.grosskopf)\
**Post date:** [May 31, 2017, 8:37am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/16 "2017-05-31T08:37:27Z")

</div>

wow, is there a way to see the difference, like a changelog or something?

---

<div class="post-metadata">

**Author:** ![g.grosskopf](https://help.nextcloud.com/letter_avatar/g.grosskopf/32/5_5575768a8748004e209b776fc1b2916d.png) [@g.grosskopf](https://help.nextcloud.com/u/g.grosskopf)\
**Post date:** [May 31, 2017, 8:50am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/17 "2017-05-31T08:50:54Z")

</div>

or could you maybe check if there are changes in the scripts in the root folder of the docker image? like use

docker exec -t -i your-docker-container-name /bin/bash

and in there:

cat [install-libreoffice.sh](http://install-libreoffice.sh)  
cat [start-libreoffice.sh](http://start-libreoffice.sh)

i have bad internet at the moment but will try it later on my own 🙂

especially the last line in [start-libreoffice.sh](http://start-libreoffice.sh) would be interesting

in mine it is:  
su -c “/usr/bin/loolwsd --version --o:sys\_template\_path=/opt/lool/systemplate --o:lo\_template\_path=/opt/collaboraoffice5.3 --o:child\_root\_path=/opt/lool/child-roots --o:file\_server\_root\_path=/usr/share/loolwsd” -s /bin/bash lool

update: seems like there was no really interesting change in the scripts, just found a git-repo

update2: it seems like they updated loolwsd to 2.1.1-4, will use their repo ^^

---

<div class="post-metadata">

**Author:** ![ripper17](https://help.nextcloud.com/letter_avatar/ripper17/32/5_5575768a8748004e209b776fc1b2916d.png) [@ripper17](https://help.nextcloud.com/u/ripper17)\
**Post date:** [May 31, 2017, 9:16am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/18 "2017-05-31T09:16:05Z")

</div>

cat [install-libreoffice.sh](http://install-libreoffice.sh)

```
#!/bin/sh

# Update installed packages
apt-get update && apt-get -y upgrade

# Install HTTPS transport
apt-get -y install apt-transport-https

# Install locales
apt-get -y install locales-all

# Add Collabora repos
echo "deb https://collaboraoffice.com/repos/CollaboraOnline/CODE /" >> /etc/apt/sources.list.d/collabora.list
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0C54D189F4BA284D
apt-get update

# Install the Collabora packages
apt-get -y install loolwsd code-brand

```

cat [start-libreoffice.sh](http://start-libreoffice.sh)

```
#!/bin/sh

# Fix lool resolv.conf problem (wizdude)
rm /opt/lool/systemplate/etc/resolv.conf
ln -s /etc/resolv.conf /opt/lool/systemplate/etc/resolv.conf

# Generate new SSL certificate instead of using the default
mkdir -p /opt/ssl/
cd /opt/ssl/
mkdir -p certs/ca
openssl genrsa -out certs/ca/root.key.pem 2048
openssl req -x509 -new -nodes -key certs/ca/root.key.pem -days 9131 -out certs/ca/root.crt.pem -subj "/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=Dummy Authority"
mkdir -p certs/{servers,tmp}
mkdir -p "certs/servers/localhost"
openssl genrsa -out "certs/servers/localhost/privkey.pem" 2048 -key "certs/servers/localhost/privkey.pem"
openssl req -key "certs/servers/localhost/privkey.pem" -new -sha256 -out "certs/tmp/localhost.csr.pem" -subj "/C=DE/ST=BW/L=Stuttgart/O=Dummy Authority/CN=localhost"
openssl x509 -req -in certs/tmp/localhost.csr.pem -CA certs/ca/root.crt.pem -CAkey certs/ca/root.key.pem -CAcreateserial -out certs/servers/localhost/cert.pem -days 9131
mv certs/servers/localhost/privkey.pem /etc/loolwsd/key.pem
mv certs/servers/localhost/cert.pem /etc/loolwsd/cert.pem
mv certs/ca/root.crt.pem /etc/loolwsd/ca-chain.cert.pem

# Replace trusted host and set admin username and password
perl -pi -e "s/localhost<\/host>/${domain}<\/host>/g" /etc/loolwsd/loolwsd.xml
perl -pi -e "s/<username desc=\"The username of the admin console. Must be set.\"><\/username>/<username desc=\"The username of the admin console. Must be set.\">${username}<\/username>/" /etc/loolwsd/loolwsd.xml
perl -pi -e "s/<password desc=\"The password of the admin console. Must be set.\"><\/password>/<password desc=\"The password of the admin console. Must be set.\">${password}<\/password>/g" /etc/loolwsd/loolwsd.xml

# Start loolwsd
su -c "/usr/bin/loolwsd --version --o:sys_template_path=/opt/lool/systemplate --o:lo_template_path=/opt/collaboraoffice5.3 --o:child_root_path=/opt/lool/child-roots --o:file_server_root_path=/usr/share/loolwsd" -s /bin/bash lool

```

I have absolutely no idea how to check diffs between my current docker images and the previous one, sorry.

---

<div class="post-metadata">

**Author:** ![xaasst](https://help.nextcloud.com/letter_avatar/xaasst/32/5_5575768a8748004e209b776fc1b2916d.png) [@xaasst](https://help.nextcloud.com/u/xaasst)\
**Post date:** [June 10, 2017, 11:31am UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/20 "2017-06-10T11:31:55Z")

</div>

I am at a loss here. Even though, this is supposed to be the official way to install Collabora and they’re working together officially, a lot of people seem to have problems with the Docker-Image.

I tried to install this just now on a clients’ NC server, but to no avail.

When I tried to reproduce it on my own installation (where it was working fine until today) I experienced the same thing.  
The docker image just seems to FUBARd - especially considering everything was working fine until I updated the docker image on my own server (without changing anything else on my server)…

---

<div class="post-metadata">

**Author:** ![zeigerpuppy](https://help.nextcloud.com/user_avatar/help.nextcloud.com/zeigerpuppy/32/4823_2.png) [@zeigerpuppy](https://help.nextcloud.com/u/zeigerpuppy)\
**Post date:** [July 7, 2017, 2:07pm UTC](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209/22 "2017-07-07T14:07:59Z")

</div>

I’m not sure why this is marked as solved.  
When I follow the instructions from [https://nextcloud.com/collaboraonline/](https://nextcloud.com/collaboraonline/)  
I get the error in this post.  
The docker container just keeps restarting. I am running on a clean install of ubuntu 16.04 LTS with the latest docker-ce

[Next page](https://help.nextcloud.com/t/restarting-docker-results-in-failed-to-fork-child-processes/12209.md?page=2)