Internal container registry

Configure using systemd

After successful installation, all Diffblue images point to eu.gcr.io/diffblue-cr container registry. You can change this to an internal registry if needed.

Assuming that internal registry is registry.container.company.com accessible on TCP/5000.

  1. Re-tag and push all Diffblue images to your internal registry by running the following commands in your shell:

     DIFFBLUE_CONTAINER_REGISTRY=registry.container.company.com:5000
    
     for image in $(docker images "eu.gcr.io/diffblue-cr/*" --format "{{.Repository}}:{{.Tag}}"); do
       (
         private_image=$(sed "s;eu.gcr.io/diffblue-cr;${DIFFBLUE_CONTAINER_REGISTRY};g" <<< ${image})
         docker tag ${image} ${private_image}
         docker push ${private_image}
       )
     done
    
  2. Edit the diffblue service

     sudo systemctl edit diffblue
    

    and add your registry as an environment variable:

     [Service]
     Environment=DIFFBLUE_CONTAINER_REGISTRY=registry.container.company.com:5000
    
  3. Reload systemd to apply your change in configuration:

     sudo systemctl daemon-reload
    
  4. Verify your settings:

     systemctl show --property=Environment diffblue
    
  5. Restart the diffblue service so it can use your internal registry:

     sudo systemctl restart diffblue
    

Configure using Docker Compose

Alternatively, you can update the /opt/diffblue/docker-compose.custom.yml file to add your internal container registry.

  1. Follow Step 1 as above to re-tag and push all Diffblue images to your internal registry.

  2. Update /opt/diffblue/docker-compose.custom.yml. The following example shows how to add a custom internal container registry for all Diffblue platform components.

     version: '2.2'
     services:
       application-server:
         image: "registry.container.company.com:5000/application-server"
       front-end:
         image: "registry.container.company.com:5000/front-end"
       deeptest-worker:
         image: "registry.container.company.com:5000/deeptest-worker"
    
  3. Restart the diffblue service so it can use your internal registry:

     sudo systemctl restart diffblue
    

results matching ""

    No results matching ""