leigh capili

CNI confdir config can already be mutated at a host level while VM's (or even more generally, containers) are running. That will affect the way the CNI plugins execute globally...

> Also how do I permanently keep using the docker runtime, instead of having to overload the --runtime artifact? We recently added the option for a global config file which...

> However, I think I should still invest in writing documentation on how to handle registries other than docker hub. Yes, thanks. This is the heart of the issue, and...

Thanks all for your comments. I began getting ignite working in WSL2. Windows Fast Ring Build 19631+ is needed to use the undocumented `nestedVirtualization` option in `.wslconfig`: https://github.com/microsoft/WSL/issues/4193#issuecomment-632732442 I'm using...

I've discovered that these `/dev/mapper` symlinks are maintained as a convenience by the userspace `udevd`. This usually runs on the host, but you can also run it in containers (such...

These patches remove the main blockers/caveats with running ignite under containers (like WSL2 distros): - #652 - #653 - #654 We will work on making the experience of booting a...

Thanks all for the interest in ignite. We just cut a very big release: https://github.com/weaveworks/ignite/releases/tag/v0.7.0 Ignite is very user-driven, so we'll all get what we put into it. Some @weaveworks...

That's really peculiar. When the VM's "speed up again", how is the performance? With just a small number of VM's on my WSL2 ignite host, I'm seeing effectively native bandwidth...

> seems like ignite can pull concurrently the same image and affect different uuid. Sorry, yes, this currently is a known limitation. We added locks free up contention on devicemapper...

The workaround for this is as you mentioned -- please pre-pull any shared images before you start your VM's concurrently (OS and kernel)