`local.bridged-network`

Multipass Documentation
,
1

See also: get, set, launch, networks, Create an instance with multiple network interfaces, Add a network to an existing instance, local.<instance-name>.bridged

Key

local.bridged-network

Description

The name of the interface to connect the instance to when the shortcut launch --bridged is issued.

Possible values

Any name from multipass networks.

Validation is deferred to multipass launch.

Examples

multipass set local.bridged-network=en0

Default value

<empty> ("").

Errors or typos? Topics missing? Hard to read? Let us know or open an issue on GitHub.

2

This bridged network feature is only available with lxd as the driver. If you have the default qemu driver, you’re out of luck.

3

Does the en0 in

multipass set local.bridged-interface=en0

refer to the physical interface on the host which is enslaved to the bridge?
Also, is there some way to use an existing bridge such as br0?

4

Hi @quashee. Yes, you can see what networks are available to bridge with multipass networks. And you can specify the intended --network on each launch.

1 Like
5

When I try that, I get:

networks failed: The networks feature is not implemented on this backend.

I’m on MacOS trying to run a linux instance - it was working perfectly until I upgraded to Sequoia 15.0. Now it shows the instance, but with no IP address - which is why I was trying to see if the network command might help.

6

Hi @peter-h-m-brooks , this is a known issue, I’m sorry you were affected. Our team has recently worked on a patch that you can find here: Multipass can't get instances' IPs on macOS Sequoia · Issue #3661 · canonical/multipass · GitHub
Let us know if this works for you!

1 Like
7

That’s brilliant, thank you - it’s working again now!

Even better, since the new version of multipass uses:

“/var/root/Library/Application Support/multipassd/vault/instances/[instance-name]/ubuntu-24.04-server-cloudimg-amd64.img”

instead of:

“/var/root/Library/Application Support/multipassd/qemu/vault/instances/[instance-name]/ubuntu-22.04-server-cloudimg-arm64.img”

I could just copy my old instance back and carry on as if there hadn’t been an upgrade.

Brilliant!

1 Like
8

Hi @peter-h-m-brooks

The fix for sequoia did not change any vm instance location. The folder and image path “/var/root/Library/Application Support/multipassd/vault/instances/[instance-name]/ubuntu-24.04-server-cloudimg-amd64.img” probably is for instances of other drivers. As long as you still use qemu driver (use multipass get local.driver to find out), then the image path should still be “/var/root/Library/Application Support/multipassd/qemu/vault/instances/[instance-name]/ubuntu-22.04-server-cloudimg-arm64.img”. As a result, you would not have to copy anything.