Upgrading Anchore Enterprise
Upgrading from one version of Anchore Enterprise (UI, Enterprise Services, and Anchore Engine) is normally handled seamlessly by the Helm chart, and trial docker-compose configuration files that are provided along with each release, following the general methods from the guide below.
This section is intended as a guide for any special instructions and information related to upgrading to specific versions of Enterprise.
Upgrading from Anchore Enterprise 2.1 to Anchore Enterprise 2.2
Prior to Anchore Engine 0.6.0 omitting the “feeds” section from the configuration or setting feeds.selective_sync.enabled=false in config.yaml would sync vulnerabilities, nvdv2, packages, and 3rd party feeds as well. This could result in sync errors when the feeds are not available in some configurations. In 0.6.0 that behavior has changed and will cause the system to only sync the vulnerabilities and nvdv2 feeds which are always available for all configurations, giving a better experience. If you have removed that configuration or set the selective_sync.enabled=false but want to continue to sync the packages and vulndb feeds, you will need to enable the selective sync and explicitly enable the packages and vulndb feeds in that configuration section.
The upgrade from Anchore Engine version 0.5.2 to version 0.6.0 includes an database schema update which is handled automatically. However, if your deployment has a large number of images (tens of thousands or more), the upgrade step will take some time (we’ve observed sub ten minutes) before the upgrade is complete. As with any upgrade, progress can be tracked by monitoring the anchore catalog service logs.
Upgrading from Anchore Enterprise 1.2 to Anchore Enterprise 2.X
Anchore Enterprise 2.X includes all of the services of Enterprise 1.2, plus a new UI Dashboard control, UI LDAP Integration, and an additional element called the Reporting Service. If you are using the anchore Helm Chart installation method, or upgrade by following the trial Docker Compose method, then there are no special considerations for the upgrade beyond setting (optionally” >}}) values for the new services.
For Helm based deployments, information on install/upgrade is hosted alongside the official Anchore Helm Chart
Manual / Advanced Upgrade
The default upgrade path is fully automated if you have deployed with either Helm or docker-compose using the provided guides and methods described above and there are no additional or manual steps required. If, however, you are manually deploying anchore services, there are a few new requirements that need to be met for the the 2.X UI to start up.
- The 2.X UI now requires a postgres database endpoint be added to it’s configuration file (appdb_uri), or environment variable override (ANCHORE_APPDB_URI).
- There is an optional reporting service endpoint value that should be set (reports_uri) or environment override (ANCHORE_REPORTS_URI), without which the UI will be functional, but with a disabled Dashboard control.
See the following links for the latest configuration options available to the new Enterprise 2.X components:
If you are manually deploying or using a method other than our provided installation tools, it is recommended that you inspect the latest Helm chart and/or the latest docker-compose.yaml to review the addition of the reporting service, reporting service configuration environment variables and section in the enterprise service config.yaml, and the addition of the new required configuration options to your existing UI config-ui.yaml configuration file.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.