Isolation of network of bottle into distinct namespace.

Is your feature request related to a problem? Please describe. I'm always frustrated when I use multiple WSL2 distros simultaneously because all WSL distros share a single network namespace; i.e., network interfaces, addresses, sockets, etc., are all shared between distros. This disallows me to use genie in multiple distros simultaneously.

Describe the solution you'd like It would be lovely to isolate network of bottle into distinct namespace when genie initializes which implies creating a network interface for the bottle in its network namespace. It is very desirable to allow the bottle to participate in WSL2 networking on L2 level e.g. to be able to directly participate in mDNS advertisement. Tricky part is that Hyper-V networking would only communicate with physical address of bare WSL2 (eth0), thus it's not very easy to make the bottle communicate to Internet. Thank God there are several technical solutions to do the trick.

Describe alternatives you've considered One might just enable ip forwarding in bare WSL2 and setup another private network for bottle. It has multiple downsides:

the bottle cannot advertise mDNS to Windows host
to reach the bottle Windows host needs dedicated routing table entry set up manually every time
nearly impossible to automate the setup

Additional context PoC network isolation set up by hand

Bare WSL can see genie bottle under different IPv4 address by hostname

Genie bottle can communicate Internet and Windows 10 host

Windows host addresses the bottle by hostname (using mDNS)

arkane-systems / genie

Isolation of network of bottle into distinct namespace. #197