Fix Docker build to use --load for single-platform images#140402
Merged
breskeby merged 2 commits intoelastic:mainfrom Jan 9, 2026
Merged
Fix Docker build to use --load for single-platform images#140402breskeby merged 2 commits intoelastic:mainfrom
breskeby merged 2 commits intoelastic:mainfrom
Conversation
Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
breskeby
added
>non-issue
:Delivery/Build
Collaborator
|
Pinging @elastic/es-delivery (Team:Delivery) |
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Jan 9, 2026
…0402) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Jan 9, 2026
…0402) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Jan 9, 2026
…0402) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Jan 9, 2026
…0402) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
Collaborator
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 9, 2026
…140438) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 9, 2026
…140440) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Jan 9, 2026
* upstream/main: (76 commits) [Inference API] Get _services skips EIS authorization call if CCM is not configured (elastic#139964) Improve TSDB codec benchmarks with full encoder and compression metrics (elastic#140299) ESQL: Consolidate test `BlockLoaderContext`s (elastic#140403) ESQL: Improve Lookup Join performance with CachedDirectoryReader (elastic#139314) ES|QL: Add more examples for the match operator (elastic#139815) ESQL: Add timezone to add and sub operators, and ConfigurationAware planning support (elastic#140101) ESQL: Updated ToIp tests and generated documentation for map parameters (elastic#139994) Disable _delete_by_query and _update_by_query for CCS/stateful (elastic#140301) Remove unused method ElasticInferenceService.translateToChunkedResults (elastic#140442) logging hot threads on large queue of the management threadpool (elastic#140251) Search functions docs cleanup (elastic#140435) Unmute 350_point_in_time/point-in-time with index filter (elastic#140443) Remove unused methods (elastic#140222) Add CPS and `project_routing` support for `_mvt` (elastic#140053) Streamline `ShardDeleteResults` collection (elastic#140363) Fix Docker build to use --load for single-platform images (elastic#140402) Parametrize + test VectorScorerOSQBenchmark (elastic#140354) `RecyclerBytesStreamOutput` using absolute offsets (elastic#140303) Define bulk float native methods for vector scoring (elastic#139885) Make `TimeSeriesAggregate` `TimestampAware` (elastic#140270) ...
jimczi
pushed a commit
to jimczi/elasticsearch
that referenced
this pull request
Jan 12, 2026
…0402) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
breskeby
added a commit
that referenced
this pull request
Jan 13, 2026
…140439) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
breskeby
added a commit
that referenced
this pull request
Jan 13, 2026
…140437) Add --load flag to single-platform Docker builds to ensure images are loaded into the local Docker daemon as regular images rather than manifest lists. This fixes an issue with Docker 23.0+ where BuildKit-enabled builds can create manifest lists even for single-platform builds, which breaks the docker manifest create command that expects single-platform images as input when creating multi-arch manifests. The --load flag forces the built image to be loaded into the local Docker image store, preventing it from being stored as a manifest list.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add --load flag to single-platform Docker builds to ensure images are
loaded into the local Docker daemon as regular images rather than
manifest lists.
This fixes an issue with Docker 23.0+ where BuildKit-enabled builds
can create manifest lists even for single-platform builds, which breaks
the docker manifest create command that expects single-platform images
as input when creating multi-arch manifests.
The --load flag forces the built image to be loaded into the local
Docker image store, preventing it from being stored as a manifest list.