2.2 KiB
layout, title, parent, nav_order
| layout | title | parent | nav_order |
|---|---|---|---|
| default | Update | Docker Compose | 1 |
Updating AliasVault
{: .no_toc }
{: .note }
This guide is for Docker Compose manual installations. If you're using the install.sh script for self-hosted installations, see Install Script Update Guide.
Table of contents
{: .text-delta } 1. TOC {:toc}Before You Begin
You can see the latest available version of AliasVault on GitHub.
{: .warning }
Before updating, it's recommended to backup your database and other important data. You can do this by making
a copy of the database and certificates directories.
Standard Update Process
For most version updates, you can use the standard update process. The container will automatically handle database migrations on startup:
- Navigate to your AliasVault directory:
cd /path/to/your/aliasvault
- Pull the latest Docker image:
docker compose pull
- Restart the container with the new image:
docker compose down && docker compose up -d
Version-Specific Upgrade Guides
While database migrations are automated, some releases may require manual file/config migration steps. Always check this page before updating to ensure you don't miss any required manual steps.
Currently there are no version-specific manual migration steps required for the single container setup. Check back here when updating to ensure you haven't missed any new requirements.
Additional Update Options
Installing a Specific Version
If you need to install a specific version instead of the latest, you can do the following. Note: downgrading to a previous version is not officially supported and may lead to unexpected issues, as database schema changes may prevent older versions from working correctly.
- Edit your
docker-compose.ymlfile - Change the image tag from
:latestto a specific version:
# ...
image: ghcr.io/aliasvault/aliasvault:0.23.0 # Replace with desired version
# ... rest of configuration
- Pull and restart:
docker compose pull
docker compose down && docker compose up -d