Skip to main content

Odoo Image Updates

Every Skysize environment runs a platform image: a container image that bundles Odoo itself, the enterprise addons for enterprise projects, and the platform modules. Skysize rebuilds these images every week from the latest upstream commits of your Odoo version, so security fixes and bug fixes reach you without you touching your code.

Each build is immutable and identified by a build tag such as 19.0-20260913-0400. Your environments run a specific build. Nothing changes under a running production environment until an image update is applied to it.

What you see​

On the production and staging environment pages, the Odoo image card shows:

  • Running: the build the environment runs, when it was built, and the upstream Odoo (and enterprise) commits it contains.
  • Newest build: the most recent build available for your Odoo version and edition.
  • A status badge: Up to date, Newer build available, or Update queued.

Comparing the two commit lists tells you exactly which upstream changes an update would bring.

Choosing how production is updated​

In Project settings, the Odoo image updates setting applies to the production environment:

  • Automatic: production moves to the newest build every week, in the platform maintenance window of your region.
  • Manual: production stays on its build until you update it yourself with Update image. You choose the moment, and optionally a specific build from the recent ones.

Staging environments always run the newest build, whatever the project setting. That way staging shows you what production will look like after its next update.

The 30-day limit​

A production environment never runs the same image build for more than 30 days. If a manual project has not been updated by then, the platform updates it during the next maintenance window. Project admins receive a reminder by e-mail one week before that date.

This limit keeps every environment on a supported image with current security fixes, and keeps the number of image versions on a host bounded.

Updating manually​

  1. Open the production or staging environment.
  2. In the Odoo image card, click Update image.
  3. Keep Newest build selected, or pick an earlier build from the list.
  4. Confirm.

The environment is recreated on the chosen image. The platform checks that Odoo answers on the new image before switching traffic to it, and rolls back to the previous image automatically if it does not. Expect a short interruption while the container restarts. Your database and files are not touched: an image update changes the Odoo code, not your data.

Picking an earlier build is the way back if a newer build causes trouble for your customizations.

What an image update is not​

An image update does not update your own modules, and does not run a database migration. Your code is deployed through your Git branches, as described in Branch Types. Changing the Odoo major version (for example 18.0 to 19.0) is a separate migration project.