Updating Odoo

The Update Odoo button on the instance page pulls the latest patch release for the Odoo version you're on (e.g. picks up the most recent odoo:18.0 from Docker Hub, including any security fixes).

What "update" means here

This is a patch update only — within the same major version.

The Odoo project itself does major-version upgrades (database schema migrations, dropped APIs, etc.). The panel doesn't try to handle that automatically — it's risky enough that we want a human to plan it. Reach out to us when you need it.

How to use the button

1. From the dashboard, click Manage on the instance you want to update.
2. Scroll to the Actions card.
3. Click Update Odoo.
4. Confirm the browser prompt ("Pull the latest Odoo image and redeploy?").

The button does:

1. Reads the current image tag your instance is using (e.g. odoo:18.0).
2. Runs docker pull to fetch the latest from Docker Hub.
3. Compares the new image's digest to the running one:

• Same digest → no update available; flash says "Already on the latest odoo:18.0." Nothing happens to your instance.
• Different digest → CapRover redeploys your Odoo on the new image. Brief downtime (~10–30 s) while the new container starts. Flash says "Updating to odoo:18.0 (sha-12)."

What's preserved

Your data, settings, custom modules, and database stay exactly the same. The update only swaps the Odoo runtime nothing in the volumes changes.

When to use it

• After we send you a security advisory mentioning the Odoo version
• Periodically (every few weeks) to stay current
• If you're seeing unexplained Odoo bugs and want to rule out an outdated image

Caveats

• The button can be clicked anytime without checking first. If there's no update available, it's a no-op — safe.
• Upstream Odoo doesn't ship patch tags as often as some other projects. It's fine for the digest to stay the same for weeks.
• It does not update Postgres. The Postgres image (postgres:12-alpine) is fixed. If you need a newer Postgres, that's a major change that needs a planned upgrade — talk to support.
• It does not update the SFTP sidecar. Same idea — the sidecar useslscr.io/linuxserver/openssh-server:latest, which we'd update via a panel deploy later.

What if the update breaks something?

Restart the instance once (Restart Instance) — sometimes Odoo just needs another start with the new image. If it still misbehaves:

1. Take note of the short-sha shown when you updated (or check the audit log).
2. Contact support — we can roll the image back. The volumes (your data) are safe; we're only reverting the runtime. Major Odoo regressions are rare — but they happen. We can usually have you back on a working version within minutes.

Updated on: 13/05/2026