Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

Livepatch on-prem patch storage

Livepatch server supports several different drivers for storing patch files downloaded from livepatch.canonical.com:

  1. Local filesystem
  2. Swift
  3. S3 (and compatible implementations, e.g. minio)
  4. Postgresql

The filesystem patch store is easiest to deploy and suits most configurations. However, if there is a need to scale out the livepatch server such as have multiple livepatch servers running to handle the load, the filesystem patch store should not be used.

In case there is a need to scale out livepatch on-prem, use the s3, postgresql or swift patch stores. Any patch store should have enough space for storing livepatches - currently at least 45GB for all patches, see this guide to filter patches sent to your on-prem instance to specific kernel variants/architectures and lower this requirement.

See the patch storage config for all available parameters.

This page was last modified a month ago. Help improve this document in the forum.