Closed tschaffter closed 8 months ago
No response
The issue is because I tried to go back to dind (docker-in-docker) for the CI workflow in #2011 and the container does not have access to the authorization.
See also:
fd1e274ce8e88044954977e554afda5d196d2469
Fixes a few sprints ago.
Is there an existing issue for this?
What projects are you seeing the problem on?
No response
Current behavior
The issue is because I tried to go back to dind (docker-in-docker) for the CI workflow in #2011 and the container does not have access to the authorization.
See also:
Expected behavior
No response
Anything else?
No response
Commit ID
fd1e274ce8e88044954977e554afda5d196d2469
Are you developing inside the dev container?
Code of Conduct