Fix CI fail with download_localhost#11315
Fix CI fail with download_localhost#11315k8s-ci-robot merged 1 commit intokubernetes-sigs:masterfrom
download_localhost#11315Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yankay The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
27ee765 to
8338363
Compare
8338363 to
ac45bd4
Compare
|
/ok-to-test |
ac45bd4 to
e5641d9
Compare
55f4e9c to
0bdeb61
Compare
download_localhost
.gitlab-ci/packet.yml
Outdated
| when: on_success | ||
| variables: | ||
| # This will instruct Docker not to start over TLS. | ||
| DOCKER_LOCALHOST_ENABLE: "true" |
There was a problem hiding this comment.
We have docker:26.1.4-dind in the service. (GitLab CI)
I'm wondering if we just need to add the DOCKER_HOST variable so that we don't need service docker start.
| DOCKER_LOCALHOST_ENABLE: "true" | |
| DOCKER_HOST: tcp://docker:2375 |
FYI: https://stackoverflow.com/questions/45316098/connecting-to-docker-in-docker-from-a-gitlab-ci-runner
(Or maybe I'm misunderstanding this fix.)
download_localhostdownload_localhost
807bddb to
0166751
Compare
Signed-off-by: Kay Yan <kay.yan@daocloud.io>
0166751 to
e0ae3c7
Compare
download_localhostdownload_localhost
|
/lgtm |
Signed-off-by: Kay Yan <kay.yan@daocloud.io>
|
/cherrypick release-2.25 |
|
@tico88612: new pull request created: #11382 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: Kay Yan <kay.yan@daocloud.io>
Signed-off-by: Kay Yan <kay.yan@daocloud.io>
What type of PR is this?
What this PR does / why we need it:
Fix CI with fail docker pull in gitlab runner by change
docker_hostvarWhich issue(s) this PR fixes:
Fixes #11313
Special notes for your reviewer:
Does this PR introduce a user-facing change?: