-
Notifications
You must be signed in to change notification settings - Fork 124
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
provisioning: Add getting started on Vultr tutorial #71
Conversation
I don't typically create instances via CLI, but I did test it out for this using my Vultr image (hosted elsewhere, pending FCOS pipeline publishing) and a small Ignition config with just an SSH authorized key setup. It provisioned and I'm able to login (with cloud firewall rule added). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - a few questions for my education.
We should probably hold this until it's actually downloadable from the getfedora.org page. (I added a corresponding checkbox in coreos/fedora-coreos-tracker#355). |
* Add Provisioning Fedora CoreOS on Vultr docs that shows uploading a snapshot image and creating an instance using the `vultr-cli` * Ignition config must include SSH authorized key setup Related: coreos/fedora-coreos-tracker#355
agree. Thanks @dghubble - we'll merge this when the next round of releases comes out. |
hmm was just about to re-look at merging this but I still don't see vultr on the download page. |
Vultr images show up in meta.json, but it seems a few more pieces are missing coreos/fedora-coreos-tracker#355 (comment) |
The website is now showing Vultr artifacts: https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable. |
Following the instructions here: https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-vultr/ I'm seeing the error: "Expected a raw disk image, but found: xz compressed data" So the instructions may need to be updated a little (unless I'm misreading the instructions). |
Ah yes, there is a decompress step missing. We can probably switch to use |
I see in the Vultr panel there is a new "Fedora CoreOS" server type option that requests for ignition content. So it seems like the Vultr team have added native support for Fedora CoreOS already. Update: I can confirm that Vultr's native Fedora CoreOS option is working as expected. I am able to provision FCOS 32 with custom ignition. |
vultr-cli
Related: coreos/fedora-coreos-tracker#355