If you are using Hashicorp (IBM 
) Packer and you notice the web server it spins up for your packer build to connect back to is using a 169 address which is an automatic private address, it will cause issues. I have run into this situation where I have virtualization solutions of some sort installed, whether Hyper-V, VMware Workstation, or Docker.
However, there is a workaround if Packer "chooses" to use a 169 address instead of your connectable address. You can add the following line to your main Packer build file, replacing the IP address with your IP address you want Packer to "listen" on.
http_ip = "10.1.149.27"