[bug]: prime-cli upgrade fails — minio/minio is no longer pullable

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Related

Related: #8774, #8820. Both discuss which storage backend to move to. This report is narrower: the current image reference breaks upgrades today.

Current Behabvior

sudo prime-cli upgrade to v3.2.0 on a Commercial Edition instance fails during "Downloading latest Plane assets" with:

Upgrade Failed, previous installation intact.
Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

At that point several images had already downloaded successfully (commercial images, postgres:15.7-alpine, valkey:7.2.11-alpine). minio:latest is the entry that errors, and the upgrade aborts.

Root cause

The compose file distributed by prime-cli contains:

plane-minio:
  image: minio/minio:latest

MinIO stopped publishing Community Edition Docker images in October 2025 and archived the repository on 25 April 2026.

Our instance continues to run — minio/minio:latest is still present in the local Docker image cache. The failure surfaces on upgrade.

Steps to reproduce

Step to reproduce

1. Commercial Edition instance installed via prime-cli, currently running
2. sudo prime-cli upgrade, confirm the upgrade to v3.2.0
3. Aborts during asset download with the error above

Workarounds tried

A docker-compose.override.yml setting pull_policy: never on plane-minio
does not help. It is visible in docker compose config, but the upgrade fails
identically, so prime-cli does not appear to read it. Editing docker-compose.yml
directly is not a durable option, as prime-cli replaces it on upgrade.

Environment

Production

Browser

None

Edition

Commercial

Version

v3.1.4