Need to delete the virtual bridge when multipassd shuts down #75
Comments
|
This also happens when someone switches from beta to edge channel when using the snap. |
6 tasks
townsend2010
pushed a commit
to townsend2010/multipass
that referenced
this issue
Feb 12, 2018
townsend2010
pushed a commit
that referenced
this issue
Feb 12, 2018
albaguirre
pushed a commit
to albaguirre/multipass
that referenced
this issue
Jun 22, 2018
Release 2018.2.1 - support JSON output in the CLI (canonical#65) - switch to using a file socket for daemon-client IPC - refactor ssh code and add unit tests for it - switch to a patched libssh fork - improve mount performance (canonical#99) - fix bash completion for mounts (canonical#40) - wait for cloud-init on start (canonical#41) - sanitize mount targets (canonical#17, canonical#47) - support proxy configuratiion (canonical#53) - default to a 5GB rootfs (canonical#29) - randomize bridge subnet (canonical#49) - fix a handful of mount bugs (canonical#71, canonical#64, canonical#78, canonical#77, canonical#83, canonical#82, canonical#81, canonical#104, canonical#105) - add `--all` option to `info` (canonical#73) - clean up networking on shutdown (canonical#75) - set a 10s timeout for download progress (canonical#108) - support rebooting instances (canonical#50) - rename `connect` to `shell` to align with lxd (canonical#115)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is possible to get into a situation where multipassd tries to use a different subnet than what the existing mpbr0 device is using. This mainly affects develops, but for correctness, the bridge should be removed when multipassd exits.
We should also clean up the routing and iptables when multipassd exits.
The text was updated successfully, but these errors were encountered: