gitlab-autodevops.md

@@ -77,12 +77,12 @@ To configure Container Registry follow official guide [here](https://gitlab.labr
 
 To enable autodevops for GitLab follow the official guide [here](https://docs.gitlab.com/ee/topics/autodevops/quick_start_guide.html#enabling-auto-devops).
 
-### Build issues:
+### Build issues
 
 1.  If your registry is not working correctly your build will fail at push stage. Check that you have done [Container Registry domain configuration](#container-registry-domain-configuration)
 ![image](/uploads/07f5df2ab9a22b0bf8c00f13d1f3c9d2/image.png)
 
-### Production issues:
+### Production issues
 
 1.  If your production fails:
 ![image](/uploads/1cc68509c4fea91d4240bc763339bfa7/image.png)
@@ -90,10 +90,18 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi
 * You can disable Auto Devops from Settings -> CI/CD:
 ![image](/uploads/60e5acf099994cf1552c3a89dd14595b/image.png)
 
-* Choose `CI/CD configuration` from your project
+* Choose `CI/CD configuration` from your project and:
  * Choose template: .gitlab-ci.yml
  * Apply a template: Auto-DevOps
  * edit the file like on **Line 45**
 ![image](/uploads/6274a11260a4c47cacb84dab6c65c0b9/image.png)
 
+### Container scanner issues
+
+1.  If your container scanner gives following issue:
+
+* You can follow [Production issues](#production-issues) set up to modify your `.gitlab-ci.yml`.
+* Edit lines 472 and 473 to use `localhost:6060` instead of `docker:6060`:
+![image](/uploads/b4c8b6fb63895db3a910b945b4223720/image.png)
+