Ian Eyberg

you have a few different issues here: 1) i wouldn't run this as root but if it makes things easier for you then for testing that's ok - I would...

ok - so for promox you should not be trying to set up the networking - that's only if you were trying to run your own infrastructure - the way...

so it looks like there might be a hard-coded default this was tested on proxmox-ve 7.1 - i do see that 7.2 is out looking at api docs https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/qemu it...

you might be hitting a different issue with the .iso suffix as that looks like it should be getting set here: https://github.com/nanovms/ops/blob/master/proxmox/proxmox_image.go#L67 the image can't be ran as a cdrom...

https://github.com/nanovms/ops/pull/1358

i fixed the .iso extension issue - at some point in the past half year or so we had removed all extensions which broke that but proxmox requires it; also...

this https://github.com/nanovms/ops/pull/1363 fixes the case where an image isn't built locally yet before trying to upload to proxmox - it ensures the image is built first which is the default...

so some thoughts (as someone who doesn't work day to day with proxmox): 1) most of our targets (like gcp or aws) don't set bridge name - instead they set...

also - attaching virtio disk has the same issue -> https://github.com/nanovms/ops/blob/master/proxmox/proxmox_instance.go#L123-L132

so we basically created a clone of elixir for this package - if you look at the manifest you can see what exactly is being executed: ``` eyberg@box:~/test/kv$ cat ~/.ops/packages/eyberg/elixir_1.8.1/package.manifest...