Martin Honermeyer

Can anyone create a pull request for this change? I currently do not have much time for this.

Running `top` inside the freshly started container shows me that the `neko` process uses 80% CPU while everything else stays close to 0.

Yeah, when connected it seems to go a bit over 100% depending on what is happening in the session, but not much more. So is idling at 80% CPU expected...

I suppose that one is built from your [dev branch](https://github.com/nurdism/neko/compare/master...m1k1o:dev)?

Oops, how did I make that connection ;)

So the question is if there is a tangible reason for this behaviour in the nurdism version or if the image build is somehow borked. I can e.g. see that...

Confirming that when using `m1k1o/neko:latest`, the `neko` process stays below 1% of CPU when idling.

Okay, and `latest` is always a firefox image? I can't discern that from the build script.

Okay, to be honest, I had to switch to host networking because I am using docker swarm mode. [Which has massive problems forwarding big port ranges](https://github.com/moby/moby/issues/11185). So at first I...

@emcgee The second approach is the one I went with. It is, while rather ugly, even possible to use this existing image for that: ``` services: synapse: image: silviof/docker-matrix:latest networks:...