Closed Matcham89 closed 1 year ago
Hi, I am not able to reproduce this on either Intel or ARM docker, please see attached:
If you are still facing this issue, please open a support ticket so the support team can investigate further.
As for the image size issue, this is a problem with the developer hub, not the image itself. The image sizes are correct on Dockerhub: https://hub.docker.com/layers/cimg/openjdk/17.0.8/images/sha256-636ba84fbc06da072f6c48b0be7ef205de36eb1091f090c9b7255f6d95d8350c?context=explore
I would suggest opening an issue with the docs team here: https://github.com/circleci/circleci-docs
As this cannot be reproduced, I will close this issue, please contact support if this is still occurring. Thanks!
Note: We also welcome PRs to fix bugs! This helps us take action faster where a bug has been identified!
For our official CircleCI Docker Convenience Image support policy, please see CircleCI docs.
This policy outlines the release, update, and deprecation policy for CircleCI Docker Convenience Images.
Describe the bug A clear and concise description of what the bug is.
Since the update to 17.0.8, the CircleCi pipeline is failing to find the image This happens when you define
17.0
or17.0.8
It can not find the image
Typically the "17.0" should bring through the latest version, but since the update on 20/07/23, the pipeline fails.
Looking at the below URL
17.0.8
is ZERO in size https://circleci.com/developer/images/image/cimg/openjdk?utm_source=google&utm_medium=sem&utm_campaign=sem-google-dg--emea-en-dsa-tROAS-auth-brand&utm_term=g_-_c__dsa_&utm_content=&gclid=Cj0KCQjw2eilBhCCARIsAG0Pf8tcuFLmKZ2Ohy6IFxMaTfcEuvE4fss5M5uSqfGj6HDX5oBMyAlWs90aAhPdEALw_wcBTo Reproduce Please provide steps to reproduce the behavior, such as a sample job or config file.
Run config.yml file with the below as the default executor
Expected behavior A clear and concise description of what you expected to happen.
The default executor with pull the latest version and work without error
Workarounds Are there any current workarounds for this bug that can be used currently?
hardcode the version to the previous 17.0.7
Screenshots and Build Links If possible, add screenshots and links to jobs to help explain your problem.
Add any other context about the problem here.
Additional context