There are lot's of online services for scanning images for vulnerabilities. These require the image to be pushed to a registry. The method outlined in alpine-cvecheck allows the user to scan the image at build time and report vulnerabilities before pushing the image. This is specific to alpine images and is not bullet-proof
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/336
**Author:** [@tomwillfixit](https://github.com/tomwillfixit)
**Created:** 5/11/2017
**Status:** ✅ Merged
**Merged:** 5/15/2017
**Merged by:** [@veggiemonk](https://github.com/veggiemonk)
**Base:** `master` ← **Head:** `patch-1`
---
### 📝 Commits (2)
- [`944c39c`](https://github.com/veggiemonk/awesome-docker/commit/944c39c84aebd5632b7a8b27bdefee20dd065427) Using Multi Stage builds to CVE scan alpine images
- [`70c947e`](https://github.com/veggiemonk/awesome-docker/commit/70c947e83b143dd8300133712495ad6be326f405) Changes based on feedback
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
<!-- Congrats on creating an Awesome Docker entry! 🎉 -->
<!-- Please fill in the below placeholders -->
**https://github.com/tomwillfixit/alpine-cvecheck**
**There are lot's of online services for scanning images for vulnerabilities. These require the image to be pushed to a registry. The method outlined in alpine-cvecheck allows the user to scan the image at build time and report vulnerabilities before pushing the image. This is specific to alpine images and is not bullet-proof**
# By submitting this pull request I confirm I've read and complied with the below requirements.
**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**
- I have read and understood the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
- The project submitted is conform to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
- Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md) and read it again.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/336
Author: @tomwillfixit
Created: 5/11/2017
Status: ✅ Merged
Merged: 5/15/2017
Merged by: @veggiemonk
Base:
master← Head:patch-1📝 Commits (2)
944c39cUsing Multi Stage builds to CVE scan alpine images70c947eChanges based on feedback📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
https://github.com/tomwillfixit/alpine-cvecheck
There are lot's of online services for scanning images for vulnerabilities. These require the image to be pushed to a registry. The method outlined in alpine-cvecheck allows the user to scan the image at build time and report vulnerabilities before pushing the image. This is specific to alpine images and is not bullet-proof
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
I have read and understood the contribution guidelines
The project submitted is conform to the quality standards outlined in the contribution guidelines
Go to the contribution guidelines and read it again.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.