Abacn opened a new issue, #27521:
URL: https://github.com/apache/beam/issues/27521

   ### What needs to happen?
   
   The current 
[publish_docker_images](https://github.com/apache/beam/blob/master/release/src/main/scripts/publish_docker_images.sh)
 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
   ```bash
   
   IMAGES=$(docker search apache/beam_ --format "{{.Name}}" --limit 100)
   ```
   then inside the loop,
   ```bash
   
   if ! docker pull "${IMAGE}:${RELEASE}${RC_VERSION}" ; then
     continue
   fi
   ```
   
   this has two minor issue though
   - 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


-- 
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]

Reply via email to