How to automate deployment using HyperV?

[Flightkick]

In order to get a development environment going I've been trying to automate deployment of a Talos (v1.1) cluster using HyperV.

My environment:
The toolstack I'm using for this is as follows:

• Windows 10 Pro 21H2
• Hashicorp Packer to build the HyperV box
• Hashicorp Vagrant to deploy the box on the local HyperV hypervisor for the development environment*
• Hashicorp Terraform for environment agnostic deployment, with the bmatcuk/vagrant provider to deploy infrastructure on development environments.

* Sidenote: Using Vagrant comes with some challenges as it is opinionated in assuming an SSH connection will be available. I could probably work around that by disabling the communicator and using post-hooks to configure and finalize the deployment. But this is not an issue for now.

The issue
The main issue I'm facing is that, when Talos is deployed to HyperV, the VM won't advertise it's IP address to the hypervisor.
I found a somewhat related post which explains that on Ubuntu, certain packages are necessary to make this work.
This behavior is the same whether the VM is deployed by Vagrant or manually using the New-TalosVM Powershell module.
In case anyone would like to replicate, the original Powershell module didn't work for me as it was missing some configuration.
Check my PR if the original module doesn't work for you.

I'm not that familiar with Talos Linux, but if I understand the docs correctly I would assume I could use extension services for the purpose of installing such packages.

Unfortunately, and this is the crux; In order to apply this configuration, I would need to have the VM's IP address in order to communicate with it's API. Which is not available, because the VM doesn't report it's IP.

Of course I could connect to the serial console and find the IP manually but I would prefer an automated solution.
Any thoughts? Has anyone managed to get automated deployments using HyperV working?

[smira]

The system extension can be bundled into the Talos install image which solves chicken-and-egg problem here.

https://www.talos.dev/v1.1/talos-guides/configuration/system-extensions/#building-a-talos-image-with-system-extensions

[frezbo]

you'd need to create a buildx builder with extra permissions:

docker buildx create --driver docker-container --driver-opt network=host --name talos --buildkitd-flags '--allow-insecure-entitlement security.insecure' --use

[Flightkick]

That builder was already present (it was mentioned in the Makefile).
I am building inside a VM though, are there any special capabilities required maybe?

[frezbo]

it's possible the vm might not have loopback support? Try deleting the builder and re-creating with the permissions required

[Flightkick]

Loopback should work on Linux ubuntu-18 4.15.0-58-generic #64-Ubuntu, the hashicorp/bionic64 box under HyperV.

Try deleting the builder and re-creating with the permissions required

I forgot to mention, I did that already after your reply to be sure I didn't have any previous builders with the wrong permissions.
These are my current builders:

$ sudo docker buildx ls
NAME/NODE DRIVER/ENDPOINT             STATUS   PLATFORMS
talos *   docker-container
  talos0  unix:///var/run/docker.sock inactive
default   docker
  default default                     running  linux/amd64, linux/386

I'm not sure if the output from the mount command is that sparse or if imager hides other essential information. The /bin/installer binary from the ghcr.io/siderolabs/imager:v1.2.0-alpha.1-23-g4fd676c04 image doesn't seem to expose any kind of --verbose flags.
Am I correct that the Imager is closed source? I couldn't find any, this makes it a bit harder to figure out what's happening.

I'm going to submit the issues I've found so far which can be helpful if anyone cares to reproduce.
Thanks for your help so far, if you or anyone else got some more idea's I'd be happy to hear them 🙂

[Flightkick]

Issues reported:

• make image-metal fails under WSL2. #6029
• make image-metal fails on shallow clone. #6030
• Makefile $(USERNAME) hides system username. #6031
• Build dependencies missing crane. #6032
• Makefile TAG variable includes --dirty which breaks image pulls. #6033