Details
-
Bug
-
Status: Resolved
-
P1
-
Resolution: Fixed
-
None
-
None
Description
I'm trying to deploy Docker images for 2.28.0 RC1 as per release instructions.
https://beam.apache.org/contribute/release-guide/#deploy-docker-images-to-dockerhub
When I try the script I get following (for parameters 2.28.0 and 1).
Publish SDK docker images to Docker Hub.
================Setting Up Environment Variables===========
Which release version are you working on:
2.28.0
Which release candidate will be the source of final docker images? (ex: 1)
1
================Confirming Release and RC version===========
We are using rc1 to push docker images for 2.28.0.
Do you want to proceed? [y|N]
y
Publishing the following images: apache/beam_python3.8_sdk
apache/beam_python3.7_sdk
apache/beam_python3.6_sdk
apache/beam_java8_sdk
apache/beam_java11_sdk
apache/beam_flink1.12_job_server
apache/beam_flink1.11_job_server
apache/beam_flink1.8_job_server
apache/beam_flink1.10_job_server
apache/beam_flink1.9_job_server
apache/beam_spark_job_server
Make sure the images are correct, then press any key to proceed.
"docker pull" requires exactly 1 argument.
See 'docker pull --help'.
Usage: docker pull [OPTIONS] NAME[:TAG|@DIGEST]
I tried adding quotes to Docker commands but then I get following.
Publish SDK docker images to Docker Hub.
================Setting Up Environment Variables===========
Which release version are you working on:
2.28.0
Which release candidate will be the source of final docker images? (ex: 1)
1
================Confirming Release and RC version===========
We are using rc1 to push docker images for 2.28.0.
Do you want to proceed? [y|N]
y
Publishing the following images: apache/beam_python3.8_sdk
apache/beam_python3.7_sdk
apache/beam_python3.6_sdk
apache/beam_java11_sdk
apache/beam_java8_sdk
apache/beam_flink1.8_job_server
apache/beam_flink1.10_job_server
apache/beam_flink1.11_job_server
apache/beam_flink1.12_job_server
apache/beam_flink1.9_job_server
apache/beam_spark_job_server
Make sure the images are correct, then press any key to proceed.
invalid reference format
Probably this is a bug introduced by recent https://github.com/apache/beam/commit/34ce707370f2b0ff539e0ac24c84485aeb07207e
Assigning to Emily for now since Kyle is OOO.
Attachments
Issue Links
- links to