Yikun opened a new pull request, #39:
URL: https://github.com/apache/spark-docker/pull/39

   ### What changes were proposed in this pull request?
   This patch adds the build-args to publish workflow (we already added it in 
build workflow: https://github.com/apache/spark-docker/pull/36)
   
   ### Why are the changes needed?
   To avoid the publish issue like:
   ```
   #5 [linux/amd64 internal] load metadata for 
docker.io/library/spark:3.4.0-scala2.12-java11-ubuntu
   #5 ERROR: pull access denied, repository does not exist or may require 
authorization: server message: insufficient_scope: authorization failed
   ------
    > [linux/amd64 internal] load metadata for 
docker.io/library/spark:3.4.0-scala2.12-java11-ubuntu:
   ------
   Dockerfile:18
   --------------------
     16 |     #
     17 |     ARG BASE_IMAGE=spark:3.4.0-scala2.12-java11-ubuntu
     18 | >>> FROM $BASE_IMAGE
     19 |     
     20 |     RUN set -ex && \
   --------------------
   ERROR: failed to solve: spark:3.4.0-scala2.12-java11-ubuntu: pull access 
denied, repository does not exist or may require authorization: server message: 
insufficient_scope: authorization failed
   Error: buildx failed with: ERROR: failed to solve: 
spark:3.4.0-scala2.12-java11-ubuntu: pull access denied, repository does not 
exist or may require authorization: server message: insufficient_scope: 
authorization failed
   ```
   
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   
   ### How was this patch tested?
   Publish test in my local fork:
   https://github.com/Yikun/spark-docker/actions/runs/4899211529/jobs/8748999886
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to