By testing port_mapping isolator during a few days in a preproduction environment where a lot of container starts, sometime fails, are destroyed continuously, I faced this issue: some agents host still have their network configuration, meaning that the netns, the veth interfaces, the tc rules are there.
Here is my setup.
- Cent OS 7.2
- LTS Kernel, 4.4.21 at that time
- libnl 3.2.28
- mesos 1.0.2 compiled using:
I have logs that apparently says that at some point the container was considered as orphan (maybe due to an operation on the host, like an agent configuration update).
It would be nice if the agent isolator could handle the cleaning of that.