github-starred/awesome-docker
2
0
Fork 0
mirror of https://github.com/veggiemonk/awesome-docker.git synced 2026-03-09 07:25:57 -05:00
Code Issues 5 Packages Projects Releases 1 Wiki Activity

[PR #652] [MERGED] Adding BuildKit #738

New Issue
Closed
opened 2025-11-06 12:05:48 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 12:05:48 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/652
Author: @sudo-bmitch
Created: 12/24/2018
Status: ✅ Merged
Merged: 12/25/2018
Merged by: @veggiemonk

Base: master ← Head: patch-2

📝 Commits (1)

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

https://github.com/moby/buildkit

From their readme: "BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner." This is Docker's new build system that is shipped with the latest versions of docker while also available to run by many other projects.

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.

RULES (because you probably didn't read the guidelines):

Links will be tested with awesome_bot. Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of README.md file.

  • FORMAT
    • Use the following format: [Name](Link) - Description.
    • [Name] should be the title of the project
    • (Link) should be pointing to a GitHub repository, not to a website
    • Description. should end with a full stop/period
    • For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like By [@author](GitHub account)
  • ORDER: The entries are in lexical order (English letter order)
  • LABEL (Optional): Add one of the following icons next to the project name like [Name](Link) :icon: - Description.
    • 💲 indicates if one needs a paying subscription to use the project.
    • 🚧 indicates that the project is a work in progress/beta release.
    • 💀 indicates that the project is obsolete, but still worth mentioning it.

🔄 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/652 **Author:** [@sudo-bmitch](https://github.com/sudo-bmitch) **Created:** 12/24/2018 **Status:** ✅ Merged **Merged:** 12/25/2018 **Merged by:** [@veggiemonk](https://github.com/veggiemonk) **Base:** `master` ← **Head:** `patch-2` --- ### 📝 Commits (1) - [`d43843b`](https://github.com/veggiemonk/awesome-docker/commit/d43843b94853582940428e3b4c86b3b3fdd0aa7a) Adding BuildKit ### 📊 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/moby/buildkit From their readme: "BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner." This is Docker's new build system that is shipped with the latest versions of docker while also available to run by many other projects. # 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/.github/CONTRIBUTING.md) - The project submitted conforms to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) - Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/.github/CONTRIBUTING.md) and read it again. **RULES (because you probably didn't read the guidelines):** Links will be tested with [awesome_bot](https://github.com/dkhamsing/awesome_bot). Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of `README.md` file. - FORMAT - Use the following format: `[Name](Link) - Description.` - `[Name]` should be the title of the project - `(Link)` should be pointing to a GitHub repository, not to a website - `Description.` should end with a full stop/period - For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like `By [@author](GitHub account)` - ORDER: The entries are in lexical order (English letter order) - LABEL (Optional): Add one of the following icons next to the project name like ```[Name](Link) :icon: - Description.``` - :heavy_dollar_sign: indicates if one needs a paying subscription to use the project. - :construction: indicates that the project is a work in progress/beta release. - :skull: indicates that the project is obsolete, but still worth mentioning it. --- <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 12:05:48 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
broken-links
bug
cannot be evaluated
enhancement
health-report
help wanted
maintenance
pending-evaluation
pull-request
Mirrored from GitHub Pull Request
 question
team discussion
weekly-digest
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#738
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?