Manage LDX (Canonical documentation)

LDX containers (Ubuntu documentation)

Use LDX Profiles to Manage Virtual Machines (YouTube)

---

Modify the default LXD profile

---

The command opens the profile in your configured text editor (or nano if none is configured). The default profile cannot be deleted or renamed. It is automatically applied to new instances unless overridden by other profiles.

How to use profiles (ubuntu documentation)

---

LXD profile "stuff"

---

Show Default Profile

This command specifically targets the "default" profile and displays its configuration details. The output is a YAML representation of the profile's configuration. This includes:

• config: General settings for the profile.


• devices: Details about devices like network interfaces (e.g., eth0).
• 
  
• used_by: Lists which instances are using this profile.

Edit a Profile (default)

---

network, ports, etc.

---

From: HERE.

DHCP server from LXD (not a system DHCP server).
If you have some other DHCP server on your host, it may conflict with the one by LXD. So, show us the output of

---

Using Macvlan

---

Create a macvlan network

lxc network create <network_name> type=macvlan parent=<host_interface>

To create a macvlan network. Replace <network_name> with a name for your network and <host_interface> with the name of your host's network interface (e.g., eth0).

Configure the container to use the macvlan network

Add the macvlan network to the container's configuration using

lxc config device add <container_name> <device_name> nic nictype=macvlan parent=<network_name>

Replace <container_name>, <device_name>, and <network_name> with the appropriate values.

Assign a static IP address to the container

The container will now be able to obtain an IP address from your DHCP server or you can assign it a static IP address using

lxc config device set <container_name> <device_name> ipv4.address=<container_ip>/<subnet_mask>

Verify connectivity

You should now be able to access the container directly using its IP address on the public network.

Routing Considerations

• Ensure your router has a route for the container's subnet
  If your container is on a different subnet than your router, you need to add a route to your router that directs traffic for the container's subnet to the host machine's IP address.


• Set up static routes on the host (if needed)
  If your router doesn't automatically route traffic to the container, you might need to add static routes on the host machine. Consult your router's documentation for instructions on how to add static routes.