Updating Blank Box

Updating Blank Box

Create a complete recovery point first. For native Linux, download the Linux installation ZIP. For Docker, download the small Docker setup ZIP from Downloads. Extract into a separate folder and use your installed trusted verifier to check the new package.

Native Linux

Open a terminal in the new extracted folder:

python3 /opt/blankbox/current/release_files.py . --trusted-key /opt/blankbox/current/release-trust.json
sudo ./install-linux.sh

The installer retains your library, account, port, access mode, sources and backup settings. You can keep using your usual address.

Docker

For a locally built image, follow Switch to the official Docker image. Changing to Portainer is a separate step after the image update works.

You can switch from a locally built image to the prebuilt image using the same update steps. Copy your existing .env and supported Compose override into the new setup folder. Keep other custom Compose files and secret/config files outside that signed folder, preserving their references. Keep the same project, UID/GID, port and volume or bind folder. Relative paths must still point to the same existing folders. Keep the current container running, then run:

./upgrade-docker.sh

Use sudo ./upgrade-docker.sh if Docker requires sudo on your host. The helper verifies and pulls the signed image digest before stopping, makes a paired catalog/assets snapshot and waits for readiness. It keeps your existing numeric user, including 10001-owned installations, and saves the accepted image and IDs in .env. Failed activation restores the previous image and snapshot. New installations default to 1000:1000. Updating does not move storage or change folder ownership. A Docker manager's image-update button does not create a paired snapshot.

Sign in, refresh your browser and check a few existing items, artwork and sources. Keep the previous application/image and paired recovery snapshot.

Compatibility and rollback

Version 1.0.1 keeps API 1 and migrates supported Linux/Docker libraries to catalog schema 23. Version 1.0.0 cannot open schema 23. Returning to older code needs its paired pre-update catalog/assets snapshot; preserve later edits before restoring it. The separate experimental Windows package remains beta.8/schema 20 and cannot open the upgraded catalog.

Use the full update and rollback guide for verification, recovery preparation and rollback commands. For a saved Portainer Web editor stack, follow the Portainer update steps to keep its definition, image and recovery point together. Library recovery cannot recreate missing linked original files.

Version 1.0.1

Version 1.0.1 migrates catalog schema 22 to 23 and can consolidate clear connected duplicates in the background. Sources, copies and compatible saved details stay with the retained title. Conflicts and uncertain matches stay separate. Keep your complete pre-update catalog/assets pair: version 1.0.0 cannot read schema 23, and changing code alone does not restore the earlier arrangement. Connected matching · Recovery