Zen

Source string Source string

74/10000 · 74

The string is read only.

English Actions
Provisioning Fedora CoreOS on VMware
This guide shows how to provision new Fedora CoreOS (FCOS) nodes on the VMware hypervisor.
Fedora CoreOS supports VMware ESXi ≥ 7.0, VMware Workstation ≥ 16, and VMware Fusion ≥ 12. It may be possible to xref:provisioning-vmware.adoc#_modifying_ovf_metadata[modify the metadata of the OVF] to run in older VMware products, but compatibility and supportability cannot be guaranteed.
Prerequisites
Before provisioning an FCOS machine, you must have an Ignition configuration file containing your customizations. If you do not have one, see xref:producing-ign.adoc[Producing an Ignition File].
Fedora CoreOS has a default `core` user that can be used to explore the OS. If you want to use it, finalize its xref:authentication.adoc[configuration] by providing e.g. an SSH key.
You also need to have access to a working VMware infrastructure, supporting VMs with at least hardware version 13. The examples below use the https://github.com/vmware/govmomi/blob/v0.29.0/govc/README.md[govc] command-line tool for remote vSphere provisioning and the https://code.vmware.com/web/tool/4.4.0/ovf[ovftool] for local Workstation or Fusion provisioning.
Downloading the OVA
Fedora CoreOS is designed to be updated automatically, with different schedules per stream. Once you have picked the relevant stream, you can download the latest OVA:
STREAM="stable"
coreos-installer download -s "${STREAM}" -p vmware -f ova
Alternatively, OVA images can be manually downloaded from the https://fedoraproject.org/coreos/download/?stream=stable#baremetal[download page].
Encoding Ignition configuration
For the `vmware` provider, Ignition requires two "guestinfo" fields to be present when the VM is first booted:
`guestinfo.ignition.config.data.encoding`: the encoding of the Ignition configuration.
`guestinfo.ignition.config.data`: the content of the Ignition configuration, encoded according to the format above.
For maximum compatibility, it is recommended to use `base64` encoding and to prepare the Ignition configuration as such:
CONFIG_ENCODING='base64'
CONFIG_ENCODED=$(cat example.ign | base64 -w0 -)
An alternative to plain `base64` encoding is `gzip+base64` as described in the https://coreos.github.io/ignition/supported-platforms/[Ignition supported platforms]. This is especially useful when submitting the Ignition config via `govc` as an _inline_ argument. In that case the encoded config is limited to slightly under 128 KiB on Linux, 256 KiB on macOS, and 32 KiB on Windows (8 KiB if using `cmd.exe` or PowerShell). If your config is larger than that limit, you may be able to submit it inline after compressing it with `gzip`.
CONFIG_ENCODING='gzip+base64'
CONFIG_ENCODED=$(cat example.ign | gzip -9 | base64 -w0 -)
If your generated Ignition configuration is still too large, you will encounter an `Argument list too long` error or similar. The solution to that problem depends on whether you are working with vSphere or Workstation/Fusion.
For vSphere, instead of inlining the configuration file within your shell, `govc` allows you to specify a path to a local file with the https://github.com/vmware/govmomi/blob/main/govc/USAGE.md#vmchange[`vm.change`]-command and will handle reading and writing it internally, circumventing any shell limitations.
CONFIG_ENCODING="gzip+base64"
CONFIG_FILE="example.ign"
CONFIG_FILE_ENCODED="${CONFIG_FILE}.gzip.b64"
gzip -9c "${CONFIG_FILE}" | base64 -w0 - > "${CONFIG_FILE_ENCODED}"
govc vm.change -vm "${VM_NAME}" -e "guestinfo.ignition.config.data.encoding=${CONFIG_ENCODING}"
govc vm.change -vm "${VM_NAME}" -f "guestinfo.ignition.config.data=${CONFIG_FILE_ENCODED}" # using `-f` with a file path instead of `-e`
Using `gzip` for this solution is optional and primarily used for consistent examples.

Loading…

User avatar None

String updated in the repository
STREAM="stable"
coreos-installer download -s "${STREAM}" -p vmware -f ova
STREAM="stable"
coreos-installer download -s "${STREAM}" -p vmware -f ova
2 years ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatching line breaks: Portuguese (Brazil), Spanish

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: delimited block -
Flags
no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`", read-only
Source string location
./pages/provisioning-vmware.adoc:26
String age
2 years ago
Last updated
a year ago
Source string age
2 years ago
Translation file
pot/master/pages/provisioning-vmware.pot, string 10