You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current publish_docker_images script assumes rc images existed locally, It fetches IMAGES via docker images command which only looks up locally existed images (either built or pulled). As we have migrated to use github action to build rc images, we need to figure out a way to fetch rc images from remote.
docker cli does not support search image having specific tag, nor sort by update date
the default --limit is 25, causing some images not get listed. We can bump --limit of course, but as time goes and more image name added, it can be risky to miss some image
Please comment if there are better way to do that.
Issue Priority
Priority: 2 (default / most normal work 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
The text was updated successfully, but these errors were encountered:
What needs to happen?
The current publish_docker_images script assumes rc images existed locally, It fetches IMAGES via
docker images
command which only looks up locally existed images (either built or pulled). As we have migrated to use github action to build rc images, we need to figure out a way to fetch rc images from remote.A possible way is change the line to
IMAGES=$(docker search apache/beam_ --format "{{.Name}}" --limit 100)
then inside the loop,
this has two minor issue though
Please comment if there are better way to do that.
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: