On Thu, Nov 16, 2017 at 8:07 PM, Juliusz Chroboczek wrote:
>> Hi, myself and Justin Kilpatrick have done a lot of this kind of stuff, and
>> Docker is kind of a distraction IMO.
>
> My colleagues are divided on that subject. Matthieu is rather fond of
> Docker, while Gwendoline
You may also be interested in a quick integration test I built using
network-lab [0]
It's not a great set of unit tests like you would hope to find in a
modern language, but it does go a long way to allowing quick testing of
changes and only takes a few seconds to run.
[0]
> Hi, myself and Justin Kilpatrick have done a lot of this kind of stuff, and
> Docker is kind of a distraction IMO.
My colleagues are divided on that subject. Matthieu is rather fond of
Docker, while Gwendoline prefers nemu.
-- Juliusz
___
Hi, myself and Justin Kilpatrick have done a lot of this kind of stuff, and
Docker is kind of a distraction IMO. You're better off using raw network
namespaces. Here's a script we made to generate virtual networks with
configurable packet loss and latency from a json config format:
> I am trying to run babeld inside docker here:
> https://github.com/zoobab/babeld-in-docker
> I can't get 2 containers to see each other, and I can't figure out why
> (multicast or any ipv6 option might not be enabled by default).
> If someone can help...
Is the filesystem shared between the
5 matches
Mail list logo