Why not use systemd-nspawn to create virtual environments for every 
distribution that people want to use? It doesn't do anything significant that 
chroot didn't do but it's an easy way of doing it all including bind mounts for 
/home etc.

If you run multiple versions of python etc on a single OS image then you either 
have python running with versions of libc etc that it didn't get distribution 
developer testing on or you have a lot of hackery to get multiple versions of 
libc etc (which has potential for inconsistent results).

On my laptop I have i386 and amd64 versions of the last few Debian releases 
running under systemd-nspawn for supporting older releases. Apart from the 
wheezy libc not running with a 4.x kernel everything is fine.
-- 
Sent from my Nexus 6P with K-9 Mail.
_______________________________________________
luv-main mailing list
[email protected]
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main

Reply via email to