Operating System and Root Disk
Learn more about the Operating Systems available for Virtual Servers.
CoreWeave Cloud supports a variety of Linux distributions and Windows versions system images for Virtual Servers.
Available Operating System versions
Click the OS type tab to see all currently available OS versions. See CoreWeave System Images for more information.
- Linux
- Windows
The size of the Virtual Server's root disk size can be increased after initialization, and the operating system will automatically expand to accommodate. However, the root disk size cannot be reduced after initial deployment.
- Cloud UI
- CLI
- Terraform
Deployment method: CoreWeave Cloud UI
From the CoreWeave Cloud UI Virtual Server deployment menu, click the Operating System expandable.
Select the Operating System you'd like to run (CentOS, Rocky, Ubuntu, or Windows), and a corresponding version. Then, set the Root Disk Size using the provided slider.
You can also configure the size of the root disk of the Virtual Server from here using the Root Disk Size slider. To add a system image addition such as NVIDIA Drivers or Teradici, click the slider into the "on" position for each desired add-on.
UEFI bootloader
If you are using a custom disk image, and need to configure UEFI bootloader options, you must do so from the YAML tab on the configuration screen. This option is configured in the os.enableUEFIboot
field, which can be set to either true
or false
.
Example in plaintext:
os:definition: aenableUEFIBoot: falsetype: linux
Readiness probe
Readiness Probes are added by CoreWeave to Windows system images by default. Learn more about CoreWeave Windows Images.
The Readiness Probe toggle adds a Readiness Probe to the Virtual Server, in order to better communicate when start-up procedures have completed. Images include a simple TCP listener on a given port to communicate with the Kubernetes API.
Beneath "Operating System Additions" is the toggle to enable or disable the Readiness Probe. The probe port is set in the field beside the toggle.
Deployment method: Kubernetes CLI
Field name | Type | Description |
---|---|---|
os | Array | Top-level field. Defines the Operating System specifications for the Virtual Server. |
os.type | String | The Operating System type, whether Linux or Windows. |
os.enableUEFIBoot | Boolean | Whether or not to enable the UEFI bootloader. |
YAML example:
os:type: linuxenableUEFIBoot: false
Readiness probe
Readiness Probes are added by CoreWeave to Windows system images by default. Learn more about CoreWeave Windows Images.
The Readiness Probe parameters inside the cloudInit
block may be used to add a Readiness Probe to the Virtual Server in order to better communicate when start-up procedures have completed. Images include a simple TCP listener on a given port to communicate with the Kubernetes API, which is configured in the tcpSocket.port
field.
readinessProbe:failureThreshold: 30initialDelaySeconds: 10periodSeconds: 20tcpSocket:port: 1337
Deployment method: Terraform
The Virtual Server's Operating System options are configured as variables passed into the Virtual Server Terraform module.
You can find the name of Operating System images (vs_image
) in the System Images section.
Operating System and root disk storage configuration options
The table below describes all available configuration options for the Operating System.
Variable name | Variable type | Description | Default value |
---|---|---|---|
vs_os_type | String | The type (Windows or Linux) of Operating System with which to provision the Virtual Server. | linux |
vs_image | String | The name of the image to be used for the Operating System. | ubuntu2004-docker-master-20210601-ord1 (The Ubuntu 20.04 image stored in the Chicago region.) |
UEFI bootloading options are not currently available through use of this Terraform module.
Example in plain text:
variable "vs_os_type" {default = "linux"}variable "vs_image" {description = "OS image"default = "ubuntu2004-docker-master-20210601-ord1"}
Readiness probe
Readiness Probes are not supported by the CoreWeave Terraform module at this time. Refer to the Cloud UI or CLI methods to configure a Readiness Probe.