Dragonfly PVE autodeploy can fail on slow machines #13

🚀 Deploying Dragonfly on pyrus...

🚀 Creating LXC container and installing Dragonfly...
  Container: dragonfly (ID: auto)

  → Template not found locally, searching Proxmox repository...
  → Found matching template: debian-13-standard_13.1-2_amd64.tar.zst
  → Downloading template debian-13-standard_13.1-2_amd64.tar.zst to storage local...
  → Waiting for template download to complete...
  → Waiting for template... (5/300)
  → Template debian-13-standard_13.1-2_amd64.tar.zst is available (10s)
  → Creating new container 'dragonfly' on node 'pyrus'
  → Warning: container 'dragonfly' not found for IP lookup
  → waiting for container 'dragonfly' to get an IP and SSH (timeout: 300s)
  → Warning: container 'dragonfly' not found for IP lookup
  → IP assigned: 10.7.1.158 — now waiting for SSH
  → SSH available on dragonfly (10.7.1.158) after 17s (4 attempts)
✓ dragonfly => provisioned
* Checking Dragonfly directories
* Uploading Dragonfly binary
* Uploading OS templates
* Writing Dragonfly config
* Installing and starting Dragonfly service
* Retrieving initial admin password
  ❌ Task 'Retrieving initial admin password' failed on dragonfly: checksum failed: /var/lib/dragonfly/initial_password.txt. sha512sum: /var/lib/dragonfly/initial_password.txt: No such file or directory
  ❌ Host 'dragonfly' failed: checksum failed: /var/lib/dragonfly/initial_password.txt. sha512sum: /var/lib/dragonfly/initial_password.txt: No such file or directory

❌ Jetpack error: Playbook parsing error: 1 host(s) failed