| ... | ... | @@ -58,6 +58,7 @@ docker exec -it gitlab bash -c 'gitlab-ctl restart' |
|
|
|
**Issue 2:**
|
|
|
|
|
|
|
|
Also it seems like that if you are trying to install Helm Tiller too fast after cluster is build you may face following error and you need to just wait couple of minutes, refresh and try installing again:
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
## SSL settings
|
| ... | ... | @@ -80,20 +81,24 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi |
|
|
|
### 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)
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
### Production issues
|
|
|
|
|
|
|
|
1. If your production fails:
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
* You can disable Auto Devops from Settings -> CI/CD:
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
* Choose `CI/CD configuration` from your project and:
|
|
|
|
* Choose template: .gitlab-ci.yml
|
|
|
|
* Apply a template: Auto-DevOps
|
|
|
|
* Edit line 45 to use your domain:
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
### Container scanner issues
|
| ... | ... | @@ -102,8 +107,8 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi |
|
|
|
|
|
|
|
* 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`:
|
|
|
|

|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
### End result
|
|
|
|
|
| ... | ... | @@ -112,4 +117,5 @@ To enable autodevops for GitLab follow the official guide [here](https://docs.gi |
|
|
|

|
|
|
|
|
|
|
|
* Performance error:
|
|
|
|
|
|
|
|
 |
|
|
\ No newline at end of file |