Private Image Delivery

Registry Client

Customer-visible registry client behavior

Image Download Service

During connected install or update, Soviez.sh downloads ERP container images through Soviez’s image delivery service at registry.soviez.com.

You do not operate this service. It is part of Soviez infrastructure. This page explains what you experience on your server.

What happens on your server

When Soviez performs a connected image pull:

  1. Soviez.sh requests short-lived download authorization (entitlement-gated).
  2. Your server uses temporary credentials in an isolated Docker config — never your personal ~/.docker/config.json.
  3. The approved image is pulled and verified against the exact release you selected.
  4. Temporary credentials are deleted immediately after the pull completes.

You never receive upstream Docker Hub credentials or permanent registry passwords.

Connected vs offline

ModeImage source
Connected install/updateSoviez image delivery service
Offline updateSigned offline bundle on disk or removable media

After download

Once images are stored locally, ERP runtime does not require continuous access to the delivery service. Network outages affect new installs and updates, not an already-running Production environment.

Configuration

The delivery service URL can be overridden with SOVIEZ_REGISTRY_GATEWAY_URL in advanced deployments. Default: https://registry.soviez.com.

When downloads fail

Common causes:

  • Expired or missing license/update entitlement
  • Network or firewall blocking outbound HTTPS
  • Attempting to pull without an exact release ID
  • Temporary service unavailability

See REGISTRY_TROUBLESHOOTING.md.

Related

Source: canonical operator documentation · Permalink