Update GitLab CI docs: Add --tls=false
to docker-in-docker to avoid startup delays
#4573
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting the docker:dind service in GitLab CI without
--tls=false
leads to the following warning within the docker sidecar container:If a gitlab-ci build job accesses the docker api right at the start, the job might fail.
This behaviour has been observed with docker 20.10.9 and a kubernetes-executor for the gitlab-runner.
It can be reproduced with the pipeline job below, but the public gitlab runner from gitlab.com is not affected by this behaviour.
Therefore I suggest to provide a hint to this
--tls=false
argument within the testcontainer docs.