[
https://issues.apache.org/jira/browse/BEAM-10193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533095#comment-17533095
]
Daniela Martín commented on BEAM-10193:
---------------------------------------
[~EliasSegundo] and I have been researching and it seems that the issue is not
reproducible anymore in our tests. We found that the issue might be related to
{{docker-compose}} directly, however we weren’t able to reproduce it again.
The approach done in BEAM-7405[1][2], we think it’s good to have it, as every
time the job is ran we have a clean environment (docker config).
>From the official Google documentation[3], we couldn’t find any available
>installation of {{docker-credential-gcloud}}, so we think it’s not available
>anymore.
We will update the Jenkins image of {{docker-credential-gcr}} version to v2.1.0
and we will be monitoring the tests in case the issue of
{{docker-credential-gcloud}} appears again.
Please let us know if you have any comments or questions.
Thank you!
[1] https://issues.apache.org/jira/browse/BEAM-7405
[2] [https://github.com/apache/beam/pull/11512/files]
[3]
[https://cloud.google.com/container-registry/docs/advanced-authentication#standalone-helper]
> Install docker-credential-gcloud on Jenkins VMs
> -----------------------------------------------
>
> Key: BEAM-10193
> URL: https://issues.apache.org/jira/browse/BEAM-10193
> Project: Beam
> Issue Type: Task
> Components: build-system
> Reporter: Brian Hulette
> Assignee: Daniela Martín
> Priority: P3
>
> See BEAM-7405 (test failure currently resolved with an inelegant workaround)
> for motivation.
> {quote}
> 5. Install docker-credential-gcloud.
> This requires updating the VM image, which requires too much effort for me at
> this time.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
