officially, the only automatic integration we plan on supporting is the VM named "termina" with a container named "penguin". if you want to create other VMs/containers, you're certainly free to, but it's up to you to trigger things like mounting of those other containers or integrating the services we've provided or configuring keys/ssh access as the rest of the system expects. e.g. garcon and such are required in order to automatically integrate desktop files into the launcher. our
docs cover this a bit more, but we don't currently have docs for power users to integrate the services themselves. at this point, the code is the manual. this should improve over time, but it isn't a priority for this year.
but if something breaks, our response generally is going to be "does it work with the default Terminal/penguin container?", and people would have to do more investigation on their side to see where the problem lies. or submit CLs to fix the problem :).
yes, if you rename "penguin" to something else, i can easily see the system getting confused. i think our answer would basically be "don't do that".
as time goes on, we'll probably expand test coverage to make sure some level of basic service works with differently named VMs/containers.