CoreOS relies on the automatic update mechanism to keep the OS up to date. The following are some aspects of the CoreOS update:
The CoreOS update mechanism is based on Google's open source Omaha protocol (https://code.google.com/p/omaha/) that is used in the Chrome browser.
Either CoreOS public servers or private servers can be used as an image repository.
The dual partition scheme is used where an update is done to the secondary partition while the primary partition is not touched. On reboot, there is a binary swap from the primary to the secondary partition. This keeps the update scheme robust. If there are issues with the new image, CoreOS automatically rolls back to the working image in the other partition.
Images are signed and verified on each update.
The following screenshot shows you the steps for the automatic update: