-
Notifications
You must be signed in to change notification settings - Fork 237
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
Adding Scanner Tool to Identify Problematic Docker Images #345
Conversation
@james-crowley First off, thank you for doing this. Adding a test suite for checking the validity of all the images is a very useful addition to the repo ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, the PR looks good. A few minor comments interspersed below. Also I'd suggest that you rename 'scanner' as 'tests' folder as we are adding a bunch of tests to the Docker images.
Also can we add tests for the official images as well
@dinogun Did you want the folder structure to look like |
@james-crowley maybe adding a information what kind of check scanner performs to scanner help command is a good idea. As I understand it can : "to identify any missing images in DockerHub, identify bad manifests and identify if any images are not getting updated". So it is excepted to add it to CI build or use during local development ? From reading the README it checks already pushed images, right ? |
|
Also please rebase the PR to include the fix for the linter script. |
@grzesuav This script could be used in a couple places. First use case would be having the script run as "cron" job in Jenkins every X hours/days. This should help you easily identify any issues with images/manifests. Second use case would be integrating this into Adopt's CI/CD. After all your images/manifests have been built for nightly images, run this to verify everything got correctly published. If you want to make a more manually approach, you can just run the script locally. If any issues raise then open a GitHub issue. That last couple issues I've open have been because this script caught errors in manifests and non-published images. |
Merge Remote Tracking Branch
Merge Remote Tracking Branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
so actually we have two outstanding task(or maybe one ? ) - add it to CI pipeline /and/or/ cronjob ? |
@grzesuav I added more information on what the checks each verification "stage" does. Hope this clears some stuff up for you. @dinogun I added the Let me know what else is needed to get this PR merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
This is a Python based tool that allows user to scan all the images AdoptOpenJDK produces and identify any problematic Docker images.
This tool was made to help assist in issue #328.
Some highlights of this tool are allowing people to identify any missing images in DockerHub, identify bad manifests and identify if any images are not getting updated.