But the example of: multipass launch --network en0 --network id=bridge0,mode=manual
fails to execute and results in “Unknown options: network, network” I did copy+paste from page. I have installed latest multipass and stopped and restarted it, but no go.
There is no documented --network option for launch when looking att help text. I navigated to that page from https://multipass.run/, so docs does not seem to be up to date.
What I want is to be able to run a service in a multipass container on a machine, and still be able to access that service in that container from other machines on the network, not only the host it is running on. Docker allows for that. Yes, it is possible to do ssh tunnels, but that seems like a rather stupid solution, and not really acceptable. I cannot find any solution to do that with multipass.
It is this being completely stuck on host multipass runs on that made me ask what multipass is for. Current state makes it very limited in use IMHO.
Right, additional networks is currently in development. That page indicates that this is feature will be available starting with version 1.6. As of right now, the feature is only implemented with the VirtualBox driver on Windows and macOS and the Hyper-V driver on Windows. Linux support is in development and will be available using the LXD driver.