No network access outside of VM/LXC

Stephen Gibson

New Member
Aug 11, 2019
I have Promox running in Virtualbox on a windows machine before I move onto replacing my current single system server.

Currently the Virtualbox config for the network adapter is bridged and I have full access to network and internet in the host. I can ping the LXC from the host and I can even ping the LXC from my windows machine

However, trying to run a Ubuntu 18.04 container I can not access anything outside. The container does show up in my router devices but no IPv4 address is assigned.

I currently have a machine acting as my Pihole and DNS server, at address

My host /etc/network/interfaces:

auto lo
iface lo inet loopback

iface enp0s9 inet manual

auto vmbr0
iface vmbr0 inet static
bridge_ports enp0s9
bridge_stp off
bridge_fd 0

My LXC /etc/netplan/config.yaml:

version: 2
renderer: networkd
addresses: []
addresses: []
dhcp4: false
interfaces: [eth0]
I attached some images, can't embed them directly due to new account.


  • chrome_43ltTu8FTl.png
    23.3 KB · Views: 46
  • chrome_C0QmBGRT3Y.png
    11.6 KB · Views: 45
  • chrome_wDtCB1BuHL.png
    15.9 KB · Views: 43
For ubuntu PVE uses systemd-networkd as network configuration - check the files in `/etc/systemd/network`
Also post the output in code tags of:
* `ip link`
* `ip address`
* `ip route`
inside the container once it's started

can you ping the default gateway ( of the container?
Thanks for helping but I seemed to have magically fixed it...kind of.

I think there was some conflict between Proxmox network and netplan.

And my other configuration has not changed.

What I did was, remove the adaptor from the network tab and re-add it. Deleted all the devices added to my routers devices by dhcp and restarted everything. Working flawlessly now.
Last edited:
I also just spun up another container entering only the config stuff into the network setup step, didn't touch netplan.yaml. All working good.
Do I just not need netplan? That's just what I used on my bare metal server running ubuntu 18.04, so assumed I had to do the same.
* As said, in general PVE takes care of configuring the network of a container, if it knows how to do it (i.e. the 'ostype' is set).
* For Ubuntu (and most distributions which support it) we use systemd-networkd for network-configuration and skip the way through netplan (which afaik renders a fitting systemd-networkd file).
This follows the idea that it would make setting the network configuration quite cumbersome if you need to both set it in the hypervisor and inside the container...

hope this explains it!


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!