ripplehang commented on PR #43601:
URL: https://github.com/apache/arrow/pull/43601#issuecomment-2415617265

   @kou The failure in 
https://github.com/apache/arrow/actions/runs/11357304238/job/31590378994?pr=43601
 seems caused by the instable networkaccess to the 
https://auth.docker.io/token, is it possible to trigger this specific pipeline 
again?Thanks
   
   `  DEBUG:archery:Executing `['docker', 'compose', 
'--file=/home/runner/work/arrow/arrow/docker-compose.yml', 'build', 
'--build-arg', 'BUILDKIT_INLINE_CACHE=1', '--progress=plain', 'ubuntu-cpp']`
     --progress is a global compose flag, better use `docker compose --progress 
xx build ...
     #0 building with "default" instance using docker driver
     
     #1 [ubuntu-cpp internal] load build definition from 
ubuntu-24.04-cpp.dockerfile
     #1 transferring dockerfile: 7.06kB done
     #1 DONE 0.0s
     
     #2 [ubuntu-cpp auth] amd64/ubuntu:pull token for registry-1.docker.io
     #2 DONE 0.0s
     
     #3 [ubuntu-cpp internal] load metadata for docker.io/amd64/ubuntu:24.04
     #3 ERROR: failed to authorize: failed to fetch oauth token: unexpected 
status from POST request to https://auth.docker.io/token: 502 Bad Gateway
     ------
     failed to solve: amd64/ubuntu:24.04: failed to resolve source metadata for 
docker.io/amd64/ubuntu:24.04: failed to authorize: failed to fetch oauth token: 
unexpected status from POST request to https://auth.docker.io/token: 502 Bad 
Gateway
      > [ubuntu-cpp internal] load metadata for docker.io/amd64/ubuntu:24.04:
     ------
   Error: `docker compose 
--file=/home/runner/work/arrow/arrow/docker-compose.yml build --build-arg 
BUILDKIT_INLINE_CACHE=1 --progress=plain ubuntu-cpp` exited with a non-zero 
exit code 17, see the process log above.
   
   The docker-compose command was invoked with the following parameters:
   `


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