[PR #336] [MERGED] Using Multi Stage builds to scan alpine images for CVEs #450

New Issue

GiteaMirror · 2025-11-06T11:59:45-06:00

GiteaMirror commented

2025-11-06 11:59:45 -06:00

📋 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)

944c39c Using Multi Stage builds to CVE scan alpine images
70c947e Changes 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.}

## 📋 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   **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>

GiteaMirror added the pull-request label 2025-11-06 11:59:45 -06:00

GiteaMirror closed this issue

2025-11-06 11:59:46 -06:00

GiteaMirror referenced this issue

2025-11-06 12:01:56 -06:00

[PR #450] [MERGED] utilize »EMOJIone« for website #555

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#450