Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: docker.yml workflow failing since ~3 days (installing yarn fails) #2586

Closed
ansgarm opened this issue Feb 2, 2023 · 1 comment · Fixed by #2588
Closed

CI: docker.yml workflow failing since ~3 days (installing yarn fails) #2586

ansgarm opened this issue Feb 2, 2023 · 1 comment · Fixed by #2588
Assignees
Labels
bug Something isn't working

Comments

@ansgarm
Copy link
Member

ansgarm commented Feb 2, 2023

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Affected Resource(s)

Our Docker image is not build (e.g. adding new Terraform versions to use for testing, is blocked)

Debug Output

https://github.com/hashicorp/terraform-cdk/actions/runs/4073395671/jobs/7017276488#step:7:803

#4 2.720 W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <[email protected]>
#4 2.720 E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
#4 ERROR: process "/bin/sh -c apt-get update -y && apt-get install -y unzip jq build-essential time" did not complete successfully: exit code: 100
------
 > [2/5] RUN apt-get update -y && apt-get install -y unzip jq build-essential time:
#4 0.519 Get:11 https://deb.nodesource.com/node_14.x buster/main amd64 Packages [774 B]
#4 0.594 Err:5 https://dl.yarnpkg.com/debian stable InRelease
#4 0.594   The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <[email protected]>
#4 0.691 Get:12 https://apt.corretto.aws/ stable/main amd64 Packages [11.3 kB]
#4 0.804 Get:13 http://deb.debian.org/debian buster/main amd64 Packages [7909 kB]
#4 0.938 Get:14 http://deb.debian.org/debian-security buster/updates/main amd64 Packages [430 kB]
#4 1.007 Get:15 http://deb.debian.org/debian buster-updates/main amd64 Packages [8788 B]

#4 2.720 W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <[email protected]>
#4 2.720 E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
------
WARNING: local cache import at /tmp/.buildx-cache not found due to err: could not read /tmp/.buildx-cache/index.json: open /tmp/.buildx-cache/index.json: no such file or directory
Dockerfile:11
--------------------
   9 |     
  10 |     
  11 | >>> RUN apt-get update -y && apt-get install -y unzip jq build-essential time
  12 |     RUN curl https://raw.githubusercontent.com/pypa/pipenv/master/get-pipenv.py | python3
  13 |     RUN npm install -g @sentry/cli --unsafe-perm
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get update -y && apt-get install -y unzip jq build-essential time" did not complete successfully: exit code: 100
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c apt-get update -y && apt-get install -y unzip jq build-essential time" did not complete successfully: exit code: 100

Expected Behavior

Workflow should succeed

Actual Behavior

Workflow fails since a few days: https://github.com/hashicorp/terraform-cdk/actions/workflows/docker.yml

Steps to Reproduce

Important Factoids

Upgrading the base image in our Dockerfile could fix this. Luckily we can test this locally by running docker build

References

@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2023

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant