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

[Bug]: Docker container RC promotion missed multiarch layer #28341

Closed
15 tasks
tvalentyn opened this issue Sep 6, 2023 · 1 comment · Fixed by #28343
Closed
15 tasks

[Bug]: Docker container RC promotion missed multiarch layer #28341

tvalentyn opened this issue Sep 6, 2023 · 1 comment · Fixed by #28343
Assignees
Labels

Comments

@tvalentyn
Copy link
Contributor

tvalentyn commented Sep 6, 2023

What happened?

It appears that 2.50.0 containers are not multiarch, but 2.50.0rc2 containers were multiarch.
See: https://hub.docker.com/r/apache/beam_python3.10_sdk/tags

Work around (if anyone needs ARM images immediately): use apache-beam==2.50.0rc2 or containers associated with RC2.

Issue Priority

Priority: 2 (default / most bugs 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
@github-actions github-actions bot added the P2 label Sep 6, 2023
@tvalentyn tvalentyn changed the title [Bug]: It appears that 2.50.0 containers are not multiarch, but 2.50.0rc2 containers were multiarch. [Bug]: Docker container RC promotion missed multiarch layer Sep 6, 2023
@tvalentyn tvalentyn added this to the 2.51.0 Release milestone Sep 6, 2023
@lostluck
Copy link
Contributor

lostluck commented Sep 7, 2023

Images are re-tagged and multi arch are available. Should be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants