-
Notifications
You must be signed in to change notification settings - Fork 634
Comparing changes
Open a pull request
base repository: docker/buildx
base: 171fcbe
head repository: docker/buildx
compare: 59582a8
- 8 commits
- 20 files changed
- 4 contributors
Commits on May 16, 2024
-
build: avoid default load with --print
Signed-off-by: Tonis Tiigi <[email protected]> (cherry picked from commit fbb0f9b)
Configuration menu - View commit details
-
Copy full SHA for b77648d - Browse repository at this point
Copy the full SHA b77648dView commit details -
build: don't generate metadata file when print flag is used
Signed-off-by: CrazyMax <[email protected]> (cherry picked from commit ba26413)
Configuration menu - View commit details
-
Copy full SHA for f6e57cf - Browse repository at this point
Copy the full SHA f6e57cfView commit details -
build: exit 1 when manifest merge failed
Signed-off-by: jaihwan104 <[email protected]> (cherry picked from commit f282351)
Configuration menu - View commit details
-
Copy full SHA for f6830f3 - Browse repository at this point
Copy the full SHA f6830f3View commit details -
build: fix multiple named contexts pointing to same bake target
Contexts using target: schema are replaced by input: pointing to previous build result before build request is sent. Currently this replacement did not work if multiple contexts pointed to the same target name. Signed-off-by: Tonis Tiigi <[email protected]> (cherry picked from commit f8c6a97)
Configuration menu - View commit details
-
Copy full SHA for 3f1aaa6 - Browse repository at this point
Copy the full SHA 3f1aaa6View commit details -
vendor: update buildx to latest docker/cli
This version of docker/cli has changes to remove compose-cli wrapper and move all CLI metrics to OTEL. Signed-off-by: Jonathan A. Sternberg <[email protected]> (cherry picked from commit 4fc4bc0)
Configuration menu - View commit details
-
Copy full SHA for cf68b5b - Browse repository at this point
Copy the full SHA cf68b5bView commit details
Commits on May 22, 2024
-
build: add cache to resolvedNode
Currently it is possible for boot() to be called multiple times, resulting multiple slow requests to establish connection (eg. multiple container inspects for container driver). Signed-off-by: Tonis Tiigi <[email protected]> (cherry picked from commit 99777ea)
Configuration menu - View commit details
-
Copy full SHA for 6a84f43 - Browse repository at this point
Copy the full SHA 6a84f43View commit details -
driver: handle nil logger for bootstrap
resolveNode methods can call with nil logger. Although the results should already be cached now in resolver this makes the protection more explicit. Signed-off-by: Tonis Tiigi <[email protected]> (cherry picked from commit 035236a)
Configuration menu - View commit details
-
Copy full SHA for a3b1fae - Browse repository at this point
Copy the full SHA a3b1faeView commit details -
Merge pull request #2471 from tonistiigi/v0.14.1-picks
[v0.14] cherry picks for v0.14.1
Configuration menu - View commit details
-
Copy full SHA for 59582a8 - Browse repository at this point
Copy the full SHA 59582a8View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 171fcbe...59582a8