The Alpha channel closely tracks master and is released frequently. The newest versions of system libraries and utilities will be available for testing. The current version is Flatcar Container Linux {{< param alpha_channel >}}.
-
Create a disk image from this channel by running:
+
Download the OVF configuration file and VMDK disk image by running:
-./create-coreos-vdi -V alpha
+mkdir flatcar; cd flatcar
+wget https://alpha.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox.ovf
+wget https://alpha.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox.ovf.sig
+wget https://alpha.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox_image.vmdk.bz2
+wget https://alpha.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox_image.vmdk.bz2.sig
The Beta channel consists of promoted Alpha releases. The current version is Flatcar Container Linux {{< param beta_channel >}}.
-
Create a disk image from this channel by running:
+
Download the OVF configuration file and VMDK disk image by running:
-./create-coreos-vdi -V beta
+mkdir flatcar; cd flatcar
+wget https://beta.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox.ovf
+wget https://beta.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox.ovf.sig
+wget https://beta.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox_image.vmdk.bz2
+wget https://beta.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox_image.vmdk.bz2.sig
The Stable channel should be used by production clusters. Versions of Flatcar Container Linux are battle-tested within the Beta and Alpha channels before being promoted. The current version is Flatcar Container Linux {{< param stable_channel >}}.
-
Create a disk image from this channel by running:
+
Download the OVF configuration file and VMDK disk image by running:
-./create-coreos-vdi -V stable
+mkdir flatcar; cd flatcar
+wget https://stable.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox.ovf
+wget https://stable.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox.ovf.sig
+wget https://stable.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox_image.vmdk.bz2
+wget https://stable.release.flatcar-linux.net/amd64-usr/current/flatcar_production_virtualbox_image.vmdk.bz2.sig
-After the script has finished successfully, the Flatcar Container Linux image will be available at the specified destination location or at the current location. The file name will be something like:
+## Verify and decompress the image
+
+Ensure that what you have downloaded has a good signature:
+
+```shell
+gpg --verify flatcar_production_virtualbox.ovf.sig
+gpg --verify flatcar_production_virtualbox_image.vmdk.bz2.sig
+```
+
+The disk image needs to be decompressed before use:
```shell
-coreos_production_stable.vdi
+bunzip2 flatcar_production_virtualbox_image.vmdk.bz2
```
-## Creating a config-drive
+## Deploying a new virtual machine on VirtualBox
-Cloud-config can be specified by attaching a [config-drive](https://github.com/flatcar/coreos-cloudinit/blob/master/Documentation/config-drive.md) with the label `config-2`. This is commonly done through whatever interface allows for attaching CD-ROMs or new drives.
+### Note for Windows users
-Note that the config-drive standard was originally an OpenStack feature, which is why you'll see strings containing `openstack`. This filepath needs to be retained, although Flatcar Container Linux supports config-drive on all platforms.
+The following steps use the `VBoxManage` command, which is not in the `PATH` on Windows by default. Temporarily add it to the `PATH` like so:
-For more information on customization that can be done with cloud-config, head on over to the [cloud-config guide](https://github.com/flatcar/coreos-cloudinit/blob/master/Documentation/cloud-config.md).
+```powershell
+$env:PATH += ";C:\Program Files\Oracle\VirtualBox"
+```
-You need a config-drive to configure at least one SSH key to access the virtual machine. If you are in hurry, you can create a basic config-drive with following steps:
+### Import the OVF configuration file and VMDK disk image
+
+Importing with no additional arguments will clone the disk image and use the default configuration defined in the OVF. You can give the VM a custom name and override certain properties such as the amount of memory and the number of CPUs. When giving any additional arguments, you must start them with `--vsys=0`.
```shell
-wget https://raw.github.com/flatcar/scripts/main/contrib/create-basic-configdrive
-chmod +x create-basic-configdrive
-./create-basic-configdrive -H my_vm01 -S ~/.ssh/id_rsa.pub
+VBoxManage import flatcar_production_virtualbox.ovf --vsys=0 --vmname=myflatcar --memory=4096 --cpus=4
```
-An ISO file named `my_vm01.iso` will be created that will configure a virtual machine to accept your SSH key and set its name to my_vm01.
+If you don't give a custom name, one will be generated for you and shown in the output.
-## Deploying a new virtual machine on VirtualBox
+### Resize the disk
-Use the built image as the base image. Clone that image for each new virtual machine and set the desired size.
+By default, the root filesystem will hold roughly 12GB. If this is too small, you can resize the image, and Flatcar will adjust the root filesystem at boot time. Find the disk's UUID within the VM's details:
```shell
-VBoxManage clonehd coreos_production_stable.vdi my_vm01.vdi
-# Resize virtual disk to 10 GB
-VBoxManage modifyhd my_vm01.vdi --resize 10240
+VBoxManage showvminfo myflatcar
```
-At boot time, the Flatcar Container Linux will detect that the volume size has changed and will resize the filesystem accordingly.
+Then resize the disk as required:
-Open VirtualBox Manager and go to Machine > New. Type the desired machine name and choose 'Linux' as the type and 'Linux 2.6 / 3.x (64 bit)' as the version.
+```shell
+VBoxManage modifymedium disk 1f768d59-256f-4fee-96f5-c12624d4f0f0 --resize 20480
+```
+
+### Make the VM accessible
-Next, choose the desired memory size; at least 2 GB for an optimal experience.
+If you were to start the VM now, you would not be able to log in because the automatic console login would be disabled, the SSH port would not be exposed, and no SSH keys would be added. Expose the VM's SSH port via port 2222 on the host:
+
+```shell
+VBoxManage modifyvm myflatcar --nat-pf1=ssh,tcp,127.0.0.1,2222,,22
+```
-Then, choose 'Use an existing virtual hard drive file' and find the new cloned image.
+An SSH key must be inserted into the VM by provisioning it with Ignition. First, write a [Butane configuration]
+[butane-configs] containing your public SSH key and transpile it. Then attach the transpiled configuration to the VM as a property:
-Click on the 'Create' button to create the virtual machine.
+#### Bash (Linux, macOS)
+```shell
+VBoxManage guestproperty set myflatcar /Ignition/Config "$(< config.ign)"
+```
-Next, go to the settings from the created virtual machine. Then click on the Storage tab and load the created config-drive into the CD/DVD drive.
+#### PowerShell (Windows)
+```powershell
+VBoxManage guestproperty set myflatcar /Ignition/Config (Get-Content -Raw config.ign)
+```
-Click on the 'OK' button and the virtual machine will be ready to be started.
+Unfortunately, a VirtualBox restriction limits the permitted size of such properties to just 1024 bytes. This is barely enough for an SSH key and/or a URL to a remote configuration. Anything further must therefore be done in a remote configuration. See [Ignition issue #2226](https://github.com/coreos/ignition/issues/2226) for more details.
-## Logging in
+### Start the VM
-Networking can take a bit of time to come up under VirtualBox, and the IP is needed in order to connect to it. Press enter a few times at the login prompt to see an IP address pop up. If you see VirtualBox NAT IP 10.0.2.15, go to the virtual machine settings and click the Network tab then Port Forwarding. Add the rule "Host Port: 2222; Guest Port 22" then connect using the command `ssh core@localhost -p2222`.
+Once configured as necessary, start the VM:
-Now, login using your private SSH key.
+```shell
+VBoxManage startvm myflatcar
+```
+
+This will open a window for the VM's display. You can run the VM headless instead:
+
+```shell
+VBoxManage startvm myflatcar --type=headless
+```
+
+## Logging in
+
+Assuming you're using NAT networking and have exposed SSH via host port 2222, log in using your private SSH key like so:
```shell
-ssh core@192.168.56.101
+ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l core -p 2222 127.0.0.1
```
## Using Flatcar Container Linux
@@ -128,6 +157,6 @@ Now that you have a machine booted it is time to play around. Check out the [Fla
[update-strategies]: ../../setup/releases/update-strategies
[release-notes]: https://flatcar-linux.org/releases
+[butane-configs]: ../../provisioning/config-transpiler
[quickstart]: ../
[doc-index]: ../../
-
diff --git a/content/docs/latest/provisioning/cl-config/dynamic-data.md b/content/docs/latest/provisioning/cl-config/dynamic-data.md
index fe7774a36..57491d142 100644
--- a/content/docs/latest/provisioning/cl-config/dynamic-data.md
+++ b/content/docs/latest/provisioning/cl-config/dynamic-data.md
@@ -28,9 +28,7 @@ This is the information available in each provider.
| Digital Ocean | ✓ | ✓ | ✓ | ✓ | ✓ |
| EC2 | ✓ | ✓ | ✓ | | |
| GCE | ✓ | ✓ | ✓ | | |
-| Packet | ✓ | ✓ | ✓ | | ✓ |
| OpenStack-Metadata | ✓ | ✓ | ✓ | | |
-| Vagrant-Virtualbox | ✓ | ✓ | | | |
## Custom metadata providers
diff --git a/content/docs/latest/reference/developer-guides/sdk-modifying-flatcar.md b/content/docs/latest/reference/developer-guides/sdk-modifying-flatcar.md
index 12a18a827..231e23cad 100644
--- a/content/docs/latest/reference/developer-guides/sdk-modifying-flatcar.md
+++ b/content/docs/latest/reference/developer-guides/sdk-modifying-flatcar.md
@@ -8,7 +8,7 @@ aliases:
The guides in this document aim to enable engineers to update, and to extend, packages in both the Flatcar OS image as well as the SDK, to suit their own needs.
Overarching goal of this collection of how-tos is to help you to scratch your own itch, to set you up to play with Flatcar.
-We’ll cover everything you need to make the changes you want, and to produce an image for the runtime environment(s) you want to use Flatcar in (e.g. AWS, qemu, Packet, etc).
+We’ll cover everything you need to make the changes you want, and to produce an image for the runtime environment(s) you want to use Flatcar in (e.g. AWS, QEMU, etc).
By the end of the guide you will build a developer image that you can run under qemu and have tools for making changes to the OS image like adding or removing packages, or shipping custom kernels.
Note that we chose this guide's "qemu" image target solely to enable local testing; the same process can be used to produce images for any and all targets (cloud providers etc.) supported by Flatcar.
diff --git a/content/docs/latest/setup/clusters/architectures.md b/content/docs/latest/setup/clusters/architectures.md
index 7132a8519..e2a2f671f 100644
--- a/content/docs/latest/setup/clusters/architectures.md
+++ b/content/docs/latest/setup/clusters/architectures.md
@@ -23,7 +23,7 @@ Most of these scenarios dedicate a few machines, bare metal or virtual, to runni
|------|--------------------|-------------|------------|
| Low | Laptop development | Minutes | No |
-If you're developing locally but plan to run containers in production, it's best practice to mirror that environment locally. Run Docker commands on your laptop that control a Flatcar Container Linux VM in VMware Fusion or Virtual box to mirror your container production environment locally.
+If you're developing locally but plan to run containers in production, it's best practice to mirror that environment locally. Run Docker commands on your laptop that control a Flatcar Container Linux VM in QEMU to mirror your container production environment locally.
### Configuring your laptop
@@ -51,8 +51,7 @@ systemd:
This file is used to provision your local Flatcar Container Linux machine on its first boot. This sets up and enables the Docker API, which is how you can use Docker on your laptop. The Docker CLI manages containers running within the VM, *not* on your personal operating system.
-Using the Butane Config Transpiler, or `butane` ([download][butane-download]), convert the above yaml into an [Ignition][ignition-getting-started]. Alternatively, copy the contents of the Igntion tab in the above example. Once you have the Ignition configuration file, pass it to your provider.
-In addition to providers supported by [upstream Ignition][ignition-supported], Flatcar [supports](https://github.com/flatcar/scripts/blob/main/sdk_container/src/third_party/coreos-overlay/sys-apps/ignition/files/0018-revert-internal-oem-drop-noop-OEMs.patch) cloudsigma, hyperv, interoute, niftycloud, rackspace[-onmetal], and vagrant.
+Using the Butane Config Transpiler, or `butane` ([download][butane-download]), convert the above yaml into an [Ignition][ignition-getting-started]. Alternatively, copy the contents of the Igntion tab in the above example. Once you have the Ignition configuration file, pass it to your provider. The list of providers supported by Ignition can be found [upstream][ignition-supported].
Once the local VM is running, tell your Docker binary on your personal operating system to use the remote port by exporting an environment variable and start running Docker commands. Run these commands in a terminal *on your local operating system (MacOS or Linux), not in the Flatcar Container Linux virtual machine*:
diff --git a/content/docs/latest/setup/storage/adding-disk-space.md b/content/docs/latest/setup/storage/adding-disk-space.md
index bd56e8a64..03ee01877 100644
--- a/content/docs/latest/setup/storage/adding-disk-space.md
+++ b/content/docs/latest/setup/storage/adding-disk-space.md
@@ -38,11 +38,8 @@ vmware-vdiskmanager -x 20Gb flatcar_developer_vmware_insecure.vmx
## VirtualBox
-Use qemu-img or vmware-vdiskmanager as described above. VirtualBox does not support resizing VMDK disk images, only VDI and VHD disks. Meanwhile VirtualBox only supports using VMDK disk images with the OVF config file format used for importing/exporting virtual machines.
-
-If you have have no other options you can try converting the VMDK disk image to a VDI image and configuring a new virtual machine with it:
+`VBoxManage` can easily resize VMDK disk images. You can also use qemu-img or vmware-vdiskmanager as described above.
```shell
-VBoxManage clonehd old.vmdk new.vdi --format VDI
-VBoxManage modifyhd new.vdi --resize 20480
+VBoxManage modifymedium disk flatcar_production_virtualbox_image.vmdk --resize 20480
```
diff --git a/data/adopters/adopters.yml b/data/adopters/adopters.yml
index 6254361de..3807e0f2d 100644
--- a/data/adopters/adopters.yml
+++ b/data/adopters/adopters.yml
@@ -24,12 +24,6 @@ items:
logo: "/media/companies/wipro-logo.png"
weight: 85
- - name: "Equinix Metal"
- description: "Equinix uses Flatcar as the OS for its bare metal cloud control plane, which runs in Kubernetes"
- link: "https://kinvolk.io/blog/2021/02/case-study-equinix-metal-builds-on-flatcar/"
- logo: "/media/companies/equinix-metal.png"
- weight: 80
-
- name: "DeepL"
description: '"We use Flatcar for our on-prem Kubernetes clusters to run everything from CI/CD to performance-sensitive GPU workloads."'
link: "https://deepl.com/"
diff --git a/data/references/companies.yml b/data/references/companies.yml
index 3b3d2541a..1c525291d 100644
--- a/data/references/companies.yml
+++ b/data/references/companies.yml
@@ -80,14 +80,6 @@ companies:
- flatcarCloudProvider
area:
- flatcar
- rackspace:
- name: Rackspace
- logo: rackspace.svg
- website: https://www.rackspace.com/
- type:
- - flatcarCloudProvider
- area:
- - flatcar
scaleway:
name: Scaleway
logo: scaleway.svg
@@ -217,18 +209,6 @@ companies:
- flatcarCloudProvider
area:
- flatcar
- equinixmetal:
- name: Equinix Metal
- logo: equinix-metal.png
- website: https://metal.equinix.com/
- type:
- - partner
- - sponsor
- - flatcarCloudProvider
- area:
- - kinvolk
- - flatcar
- - lokomotive
gcp:
name: Google Cloud PLatform
logo: gcp-logo.png
diff --git a/static/media/companies/equinix-metal.png b/static/media/companies/equinix-metal.png
deleted file mode 100644
index d0533be1d..000000000
Binary files a/static/media/companies/equinix-metal.png and /dev/null differ
diff --git a/static/media/companies/packet.png b/static/media/companies/packet.png
deleted file mode 100644
index 78aea754b..000000000
Binary files a/static/media/companies/packet.png and /dev/null differ
diff --git a/static/media/companies/rackspace.svg b/static/media/companies/rackspace.svg
deleted file mode 100644
index f2bbfff5d..000000000
--- a/static/media/companies/rackspace.svg
+++ /dev/null
@@ -1 +0,0 @@
-