none
Container's IP address being assigned to container host RRS feed

  • Question

  • When I start a container, it's IP address is being registered with DNS as being the IP address of the container host. Connections to the container host start failing because the rest of the network thinks it's IP address is 172.16.0.2 which is of course not reachable.

    The container host is a virtual machine running window server 2016. It sits on a hyper-v host also running 2016 build 10514. The virtual machine has been set up as a container host using the script at http://aka.ms/setupcontainers. The Virtual Switch is set to NAT with the subnetprefix 172.16.0.0/12. There are two ethernet adapters on the VM, the original adapter and one created when the virtual switch was created.

    Has anyone else experienced this issue? Is there any way to prevent this from happening?

    UPDATE:

    Inside the container itself the details of the IP address are:

    As a solution I have tried setting the SkipAsSource parameter to false but am getting an Access Denied error (the powershell session is running as administrator).

    • Edited by Shawn_S Friday, October 16, 2015 11:49 AM More info
    Friday, October 16, 2015 7:28 AM