Containerized EDR steps from installation guide not working as expected.
search cancel

Containerized EDR steps from installation guide not working as expected.

book

Article ID: 375002

calendar_today

Updated On:

Products

Carbon Black EDR (formerly Cb Response)

Issue/Introduction

After following the "Installation Prerequisite" steps from the Carbon Black EDR Containerized Server Guide, the "edr-docker" wrapper script used to install a standalone or primary cluster node fails to run.

Environment

  • Containerized EDR: Version 7.8.0
  • Linux OS: Supported Versions
  • Docker: version 20.10.14 or greater

Cause

Starting in Containerized EDR version 7.7.0, the "edr-docker" wrapper file is created and defaults to the following URL `projects.registry.vmware.com` for the image repository instead of the newer `projects.packages.broadcom.com`

Resolution

The `docker tag` cmd from the Installation Prerequisites section can be edited to tag the image correctly to be used with the wrapper script:

  1. Original documentation command: 
    docker tag projects.packages.broadcom.com/carbonblack/edr-server:7.8.0 projects.packages.broadcom.com/carbonblack/edr-server:current
     
  2. New command that should be used instead:
    docker tag projects.packages.broadcom.com/carbonblack/edr-server:7.8.0 projects.registry.vmware.com/carbonblack/edr-server:current

This `edr-docker` wrapper script is going to be updated in the 7.9.0 version of Containerized EDR; however, this workaround is applicable until that time.

Additional Information

Another option would be to create an environmental variable to point to projects.packages.broadcom.com:

export EDR_IMAGE_REGISTRY=projects.packages.broadcom.com