Return to Answer

The following worked for me:

Assign static IP address to systemd-nspawn container (private networking mode).

Note: I just modified the DHCPServer=no option because it's no needed and to prevent conflict with the dnsmasq's DHCP server running on the host in my use case.

The following worked for me:

Assign static IP address to systemd-nspawn container (private networking mode).

Note: I just modified the DHCPServer=no option because DHCP is no needed in the static IP assignment and to prevent the conflict with the dnsmasq DHCP server service running on the host in my use case.

The following worked for me:

Assign static IP address to systemd-nspawn container (private networking mode).

Note: if you are running dnsmasq on the host, you may experience a conflict with the DHCP service provided by the systemd-networkd service. Since the IPs are static, you can deactivate DHCP assignment by DHCPServer=no setting to prevent this collision.

The following worked for me:

Assign static IP address to systemd-nspawn container (private networking mode).

Note: I just modified the DHCPServer=no option because it's no needed and to prevent conflict with the dnsmasq's DHCP server running on the host in my use case.

I was not able to reach the Internet from the container neither to reach the services running inside the container from the outside despite correct mapping in the .nspawn config by following above. The problem seemed to be somehow related to the 169.254.x.x address range. Finally, this helped me setup the static IPs for the container interface (with private networking) and the host:

Assign static IP address to systemd-nspawn container (private networking mode).

Note: if you are running dnsmasq on the host, you may experience a conflict with the DHCP service provided by the systemd-networkd service. Since the IPs are static, you can deactivate DHCP assignment by DHCPServer=no setting to prevent this collision.

The following worked for me:

Assign static IP address to systemd-nspawn container (private networking mode).

Note: if you are running dnsmasq on the host, you may experience a conflict with the DHCP service provided by the systemd-networkd service. Since the IPs are static, you can deactivate DHCP assignment by DHCPServer=no setting to prevent this collision.