I’m seeing that the Docker and Container-Scanning gitlab templates point at different default images.
While playing with the Container-Scanning template I continually got permission denied errors when trying to run the following ci.
include: - template: Container-Scanning.gitlab-ci.yml - template: Docker.gitlab-ci.yml stages: - build - test
After digging for a while I realized the Container-Scanning template was by default pointing at
$CI_REGISTRY_IMAGE/master:latest while the Docker template was uploading by default to
The following template gets the two to align correctly. Is this a bug that needs to be reported? Users shouldn’t have to dig as hard as I did to figure out what makes the default CI setup with the two templates happy.
variables: CI_APPLICATION_REPOSITORY: $CI_REGISTRY_IMAGE CI_APPLICATION_TAG: latest include: - template: Container-Scanning.gitlab-ci.yml - template: Docker.gitlab-ci.yml stages: - build - test