Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate using Docker Bake to build Antrea image chain #6560

Open
4 tasks
antoninbas opened this issue Jul 26, 2024 · 1 comment
Open
4 tasks

Investigate using Docker Bake to build Antrea image chain #6560

antoninbas opened this issue Jul 26, 2024 · 1 comment
Assignees
Labels
area/build-release Issues or PRs related to building and releasing priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@antoninbas
Copy link
Contributor

Bake a feature of Docker Buildx that lets you define your build configuration using a declarative file, as opposed to specifying a complex CLI expression.

It may be a good alternative to our multiple build scripts (e.g., https://github.com/antrea-io/antrea/blob/main/hack/build-antrea-linux-all.sh). Using Bake could also help avoid issues such as this one: #6559, as when building a new image you retain access to previous images (targets) built in the same bake invokation.

Some things to look into:

  • version requirements to run Bake (all the docker versions we use in CI may not support it).
  • multi-platform support (see also Migrate Arm image building and testing to this repo #6453): can we build the image "chain" for different architectures on different machines, then create a multi-platform manifest? We would want to push a multi-platform manifest for each image in the chain.
  • does registry-based caching work well, to enable fast local and CI builds? Unlikely to be an issue.
  • can we use it to build the antrea-agent Windows image as well?
@antoninbas antoninbas added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. area/build-release Issues or PRs related to building and releasing labels Jul 26, 2024
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2024
@antoninbas antoninbas self-assigned this Oct 25, 2024
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-release Issues or PRs related to building and releasing priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

1 participant