Skip to content

Commit 540fcc4

Browse files
committed
website: network: move socket_vmnet to the bottom of the page
Signed-off-by: Akihiro Suda <[email protected]>
1 parent dd8ded2 commit 540fcc4

File tree

1 file changed

+68
-68
lines changed
  • website/content/en/docs/config/network

1 file changed

+68
-68
lines changed

website/content/en/docs/config/network/_index.md

Lines changed: 68 additions & 68 deletions
Original file line numberDiff line numberDiff line change
@@ -57,13 +57,80 @@ During initial cloud-init bootstrap, `iptables` may not yet be installed. In tha
5757

5858
If `hostResolver.enabled` is false, then DNS servers can be configured manually in `lima.yaml` via the `dns` setting. If that list is empty, then Lima will either use the slirp DNS (on Linux), or the nameservers from the first host interface in service order that has an assigned IPv4 address (on macOS).
5959

60+
## Lima user-v2 network
61+
62+
| ⚡ Requirement | Lima >= 0.16.0 |
63+
|-------------------|----------------|
64+
65+
user-v2 network provides a user-mode networking similar to the [default user-mode network](#user-mode-network--1921685024-) and also provides support for `vm -> vm` communication.
66+
67+
To enable this network mode, define a network with `mode: user-v2` in networks.yaml
68+
69+
By default, the below network configuration is already applied (Since v0.18).
70+
71+
```yaml
72+
...
73+
networks:
74+
user-v2:
75+
mode: user-v2
76+
gateway: 192.168.104.1
77+
netmask: 255.255.255.0
78+
...
79+
```
80+
81+
Instances can then reference these networks from their `lima.yaml` file:
82+
83+
{{< tabpane text=true >}}
84+
{{% tab header="CLI" %}}
85+
```bash
86+
limactl start --network=lima:user-v2
87+
```
88+
{{% /tab %}}
89+
{{% tab header="YAML" %}}
90+
```yaml
91+
networks:
92+
- lima: user-v2
93+
```
94+
{{% /tab %}}
95+
{{< /tabpane >}}
96+
97+
An instance's IP address is resolvable from another instance as `lima-<NAME>.internal.` (e.g., `lima-default.internal.`).
98+
99+
_Note_
100+
101+
- Enabling this network will disable the [default user-mode network](#user-mode-network--1921685024-)
102+
60103
## VMNet networks
61104

62105
VMNet assigns a "real" IP address that is reachable from the host.
63106

64107
The configuration steps are different for each network type:
65-
- [socket_vmnet](#socket_vmnet)
66108
- [vzNAT](#vzNAT)
109+
- [socket_vmnet](#socket_vmnet)
110+
111+
### vzNAT
112+
113+
| ⚡ Requirement | Lima >= 0.14, macOS >= 13.0 |
114+
|-------------------|-----------------------------|
115+
116+
For [VZ](../vmtype/#vz) instances, the "vzNAT" network can be configured as follows:
117+
{{< tabpane text=true >}}
118+
{{% tab header="CLI" %}}
119+
```bash
120+
limactl start --vm-type=vz --network=vzNAT
121+
```
122+
{{% /tab %}}
123+
{{% tab header="YAML" %}}
124+
```yaml
125+
networks:
126+
- vzNAT: true
127+
```
128+
{{% /tab %}}
129+
{{< /tabpane >}}
130+
131+
The range of the IP address is not specifiable.
132+
133+
The "vzNAT" network does not need the `socket_vmnet` binary and the `sudoers` file.
67134

68135
### socket_vmnet
69136
#### Managed (192.168.105.0/24)
@@ -205,70 +272,3 @@ networks:
205272
# configured in socket_vmnet and not in lima.
206273
# - socket: "/var/run/socket_vmnet"
207274
```
208-
209-
### vzNAT
210-
211-
| ⚡ Requirement | Lima >= 0.14, macOS >= 13.0 |
212-
|-------------------|-----------------------------|
213-
214-
For [VZ](../vmtype/#vz) instances, the "vzNAT" network can be configured as follows:
215-
{{< tabpane text=true >}}
216-
{{% tab header="CLI" %}}
217-
```bash
218-
limactl start --vm-type=vz --network=vzNAT
219-
```
220-
{{% /tab %}}
221-
{{% tab header="YAML" %}}
222-
```yaml
223-
networks:
224-
- vzNAT: true
225-
```
226-
{{% /tab %}}
227-
{{< /tabpane >}}
228-
229-
The range of the IP address is not specifiable.
230-
231-
The "vzNAT" network does not need the `socket_vmnet` binary and the `sudoers` file.
232-
233-
## Lima user-v2 network
234-
235-
| ⚡ Requirement | Lima >= 0.16.0 |
236-
|-------------------|----------------|
237-
238-
user-v2 network provides a user-mode networking similar to the [default user-mode network](#user-mode-network--1921685024-) and also provides support for `vm -> vm` communication.
239-
240-
To enable this network mode, define a network with `mode: user-v2` in networks.yaml
241-
242-
By default, the below network configuration is already applied (Since v0.18).
243-
244-
```yaml
245-
...
246-
networks:
247-
user-v2:
248-
mode: user-v2
249-
gateway: 192.168.104.1
250-
netmask: 255.255.255.0
251-
...
252-
```
253-
254-
Instances can then reference these networks from their `lima.yaml` file:
255-
256-
{{< tabpane text=true >}}
257-
{{% tab header="CLI" %}}
258-
```bash
259-
limactl start --network=lima:user-v2
260-
```
261-
{{% /tab %}}
262-
{{% tab header="YAML" %}}
263-
```yaml
264-
networks:
265-
- lima: user-v2
266-
```
267-
{{% /tab %}}
268-
{{< /tabpane >}}
269-
270-
An instance's IP address is resolvable from another instance as `lima-<NAME>.internal.` (e.g., `lima-default.internal.`).
271-
272-
_Note_
273-
274-
- Enabling this network will disable the [default user-mode network](#user-mode-network--1921685024-)

0 commit comments

Comments
 (0)