[Feature Request]: Build Docker images for Beam releases in a standard location

[chamikaramj]

What would you like to happen?

Currently we build Docker images for Beam releases in the local machine of the release manager.

This process is brittle and may result in Docker images that are broken or inconsistent with the Docker images that we use for tests. See #26576 for an example issue.

We should build Docker images in a standard location (for example, on a bullseye container) and use consistent images for tests and releases.

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[chamikaramj]

@damccorm is this something you can track for as a part of Beam release process improvements ?

[damccorm]

This was done as part of our release process, we now build on our actions runners