-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxmox support #1040
Comments
Hi! I'm looking at updating Would that help? |
Seems maybe the OP lost interest, but I'm about to dabble in proxmox. I'd love to be able to use flatcar in my tf deployments there. Is there anything I can do to help? |
Hi folks, we've been working on proxmoxve support for flatcar. The work has been two folds :
The work on afterburn is ok (dns, ssh-keys, ip configuration, ...), you can follow-up an eventual merge through the following PR: coreos/afterburn#1023 The work on the OEM side of things consist of installing the modified afterburn, and then using typical OEM stuff to enable proxmoxve compatibility, we are building the stable versions on a regular basis: https://github.com/enix/flatcar-proxmoxve/releases I must say we would prefer to have our work on afterburn merged, and avoid custom binary installation through the OEM partition ... hopefully it will happen at some point in the future. Then the flatcar project could build proxmoxve variants easily. In the meantime, feel free to use our images or request other builds (beta / lts / ....) |
Hey, Is there anything new? I would appreciate any help in this case. |
Pretty sure user data doesn't work in pmve like in esxi. The way I did it
|
|
@mcbenjemaa yes indeed fw_cfg requires root. Don't know of any other workaround. |
Hello folks, the Proxmox support is now available on Alpha release: https://www.flatcar.org/releases#release-4152.0.0. Thanks everyone involved on the development and the testing of this feature. The documentation is available here: flatcar/flatcar-website#337 |
Thanks a lot :) |
Proxmox does not support ignition, but one can probably trigger loading cloud-init from a static ignition file (
/var/lib/vz/snippets/ignition-run-cloud-init.json
). Passing ignition via -fw_cfg isn't solution, its just not possible for non root users, see https://forum.proxmox.com/threads/fedora-core-os-ignition-root-pam-api-tokens-restricted-from-using-qemu-args.108886/ for more info.Trying this ( via root user in proxmox ):
, but the VM cloned from this template does not fetch cloud-init settings set directly on VM via WebUI.
Debug:
Thanks
The text was updated successfully, but these errors were encountered: