The only thing I can think of is that the client does not like the docker0 virtual interface. Could you try to turn off network stats and see if that fixes it?
I don’t think ignoring would fix it as I assume the docker0 interface would create virtual interfaces for each container. Those virtual interfaces are probably the ones that the client can’t handle.
Could you confirm disabling the network counter completely stops the client from crashing when you run docker?
If so, you might want to leave it disabled when you work with it for now. I’ve put it on the todo, it might be an easy fix, it might not be.
This is a real major bug for me, as I want to track my whatpulse stuff still…
It keeps messing up my machine. If it disable/enable network, you have to reboot, otherwise it just causes crazy irq requests and sucks all your memory
Not sure, the todo list is pretty long with more stuff with a higher priority then this one, as you are maybe 1 of 5 users who use this on their local machine. Not that you get anything from this answer, but I can’t give a proper one.
Could you guys give me a bit more information about your OS (version, kernel version), docker version and network config? Trying to reproduce, not getting any crashing results.
Do you have a link to any virtual images (VMware) with Arch Linux 4.8.6? The installation is horrendous and I’m not going to take 2 hours just to install an OS…
It doesn’t always do it on the first time, but after 3-4 docker builds whatpulse normally crashes and ends up hogging the system. I can pkill the process and take control again.