I searched entire internet haven't see any solution for it yet.
I have a OVH + Proxmox instance. Plan to automatic the launch VM process. I know I can try use cloud-init but since I use Packer + (maybe) Terraform for the ESXi at home, so I want to try to use same thing for the Proxmox cloud as well.
Current setup:
- I have
packer.json, well configured. - I have a
debian-preseed.cfg.
When install ESXi, the preseed.cfg was hosted locally and use private ip. Which works well.
However, the Proxmox on OVH can't reach my local preseed, so I decide to host it on AWS S3. Then that's when the issue concurred.
Issue: the VM building Proxmox image can't reach the preseed file on AWS - https://bucket-name.s3.regions.amazonaws.com/dir/debian-preseed.cfg
I spent few hours try to figure out what's the root cause. It seems like the VM's network isn't configured properly.
I am using DHCP + Mac-To-Static IP to make installation process easier. I am pretty sure it works if I manually install the VM. However, it seems like the IP and network only reachable after debian installation?
Is there any reason this doesn't work? Should I switch to use bridge+private IP first then manually setup the public IP later once I am using it?
