damccorm opened a new issue, #35487: URL: https://github.com/apache/beam/issues/35487
### What would you like to happen? Full context here - https://docs.google.com/document/d/1JcVFJsPbVvtvaYdGi-DzWy9PIIYJhL7LwWGEXt2NZMk/edit?tab=t.0 - we should add some containers for running Beam ML jobs. Steps: - [ ] Create requirements files for these containers. These should be auto-generated like we do for other containers today - https://github.com/apache/beam/blob/master/sdks/python/container/run_generate_requirements.sh - #35484 - [ ] Automatically stage and publish CPU ML containers alongside our existing containers. This should be able to mostly reuse the existing Dockerfile with a different set of requirements - [ ] Automatically stage and publish GPU ML containers alongside our existing containers. This will require a different Dockerfile and likely will require building in a GPU environment (real or simulated) - [ ] Allow users to specify `--sdk_container_image=ml` or `--sdk_container_image=gpu` and auto-resolve to the correct container. ### 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 YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
