On 06/09, Charles Allen wrote: > We have a custom coreos build (specific portage overlay) which we use to > build our images. > > Right now we just build the image and call image_to_vm to create the cloud > volume snapshot binary blob. I would like to be able to move to something > that is compatible with the coreos partition swapping but am having trouble > finding a way to either: > > 1. Have a non-official update channel local to our organization > 2. Have a way to really-really-manually update a coreos node. > > Looking at https://coreos.com/os/docs/latest/manual-rollbacks.html it seems > it might be possible to simply update the not-in-use USR-? partition from > the "new" image and continue from there. > > Is there a way to either use a non-official update channel, or to manually > push an update into the unused USR partition?
You'll need to either purchase CoreUpdate [1] or use an open source alternative (later in the thread, you mentioned CoreRoller which appears to be a nice alternative). Once you run the omaha server, you'll need to maintain your own CA and regularly publish images to your channels. Can I ask why you are unable to use the official images? -Alex [1]: https://coreos.com/products/coreupdate
signature.asc
Description: PGP signature
