Search results

  1. Bug in resolv.conf using containers

    Alwin, I did create new container just now, step by step. Weirdly, now it worked correctly. I did make the containers that had problem a while ago, not with this particular version. Maybe it is fixed in meantime. I'm not sure what happened, it was not a 1 time thing... create CT, ct id 106...
  2. Bug in resolv.conf using containers

    Yeah I use 'Use host settings' on container creation. The host/hypervisor settings (searchdomain and dnsserver ips) are correctly set but like I said, in containers vmid.conf and as a result inside container the resolv.conf information is not set correctly. I'm quite sure it is not correctly...
  3. Bug in resolv.conf using containers

    Yes.. that *is* the bug ... ;-) I did not do that manually... It is written wrong in the LXC vmid.conf when the container is created from webgui. Instead of searchdomain it takes the IP of first dns-server, the ip of first dns server is the 2nd ip.. so everything seems moved 'up' 1 line. Config...
  4. Bug in resolv.conf using containers

    root@hypervisor:/etc/pve/lxc# cat 100.conf arch: amd64 cores: 1 hostname: server1 memory: 512 nameserver: net0: name=eth0,bridge=vmbr0,gw=172.xx.xx.254,hwaddr=xx:xx:FC:31:A5:DD,ip=172.xx.xx.101/24,type=veth onboot: 1 ostype: debian parent: beforeresize rootfs...
  5. Bug in resolv.conf using containers

    Hi It seems like i'm getting some kind of buggy behaviour inside debian9 container. resolv.conf gets rewritten with wrong info, the searchdomain contains first dns-server instead of the actual search-domain : root@debian1:~# cat /etc/resolv.conf # --- BEGIN PVE --- search nameserver...
  6. Promiscuous bridge for LXC Container?

    I am exactly running into the same issue. I do however see ARP and broadcast traffic coming through, but it looks like the 'promisc' part is being dropped before forwarding it to the container. Anyone?
  7. Ethenetcontroller hangs after upgrade to kernel 4.15.18-2-pve

    A few hours after upgrade to: Linux 4.15.18-2-pve #1 SMP PVE 4.15.18-20 (Thu, 16 Aug 2018 11:06:35 +0200) pve-manager/5.2-7/8d88e66a I got this. Aug 24 01:45:09 zpm kernel: [ 8639.650825] DMAR: [DMA Read] Request device [00:1f.6] fault addr fe537000 [fault reason 06] PTE Read access is not...


The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!