tuhaihe opened a new pull request, #155:
URL: https://github.com/apache/cloudberry-pxf/pull/155

   The pxf-s3 Testcontainers jobs fail while starting MinIO:
   
   ```
     ContainerFetchException: Can't get Docker image:
     RemoteDockerImage(imageName=minio/minio:RELEASE.2024-11-07T00-52-20Z)
     Caused by: NotFoundException: Status 404: pull access denied for
     minio/minio, repository does not exist or may require 'docker login'
   ```
   
   The minio namespace is gone from Docker Hub: both minio/minio and minio/mc 
now return "object not found", so pinning a digest would not help either. Other 
Docker Hub images such as alpine:3.17 still pull fine in the same job, so this 
is not rate limiting.
   
   MinIO still publishes the community image on quay.io, where the pinned tag 
remains available as a six-architecture manifest list. Only the registry host 
changes here, the tag is left alone on purpose: the image content stays 
identical, so the container settings and test behaviour are unaffected. Bumping 
the MinIO version is a separate concern.
   
   Note that quay.io is still an upstream we do not control. A follow-up could 
mirror the image into a registry owned by the project, similar to the image 
caching already used for MSSQL.
   
   Backpatch-through: REL_2_STABLE
   
   <!--Thank you for contributing! -->
   
   <!--In case of an existing issue or discussions, please reference it-->
   closes: #ISSUE_Number
   <!--Remove this section if no corresponding issue.-->
   
   ---
   
   ## Change logs
   
   > Describe your change clearly, including what problem is being solved or 
what document is being added or updated.
   
   ## Contributor's checklist
   
   Here are some reminders before you submit your pull request:
   
   * Make sure that your Pull Request has a clear title and commit message. You 
can take the [Git commit 
template](https://github.com/apache/cloudberry/blob/main/.gitmessage) as a 
reference.
   * Learn the [code 
contribution](https://cloudberry.apache.org/contribute/code) and [doc 
contribution](https://cloudberry.apache.org/contribute/doc) guides for better 
collaboration.
   * Make sure that CICD workflow is successful.
   * List your communications in the [GitHub 
Issues](https://github.com/apache/cloudberry-pxf/issues) or 
[Discussions](https://github.com/apache/cloudberry/discussions) (if has or 
needed).
   * Feel free to ask for the [cloudberry 
committers](https://github.com/orgs/apache/teams/cloudberry-committers) or 
other people to help review and approve.


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