[jira] [Closed] (JAMES-4102) Can't pull Zenko cloudserver S3 image anymore

"Matthieu Baechler (Jira)" <[email protected]>
Newsgroups gmane.comp.jakarta.james.devel
Message-ID <[email protected]>
     [ https://issues.apache.org/jira/browse/JAMES-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthieu Baechler closed JAMES-4102.
------------------------------------
    Resolution: Fixed

It has been fixed by https://github.com/apache/james-project/pull/2599

> Can't pull Zenko cloudserver S3 image anymore
> ---------------------------------------------
>
>                 Key: JAMES-4102
>                 URL: https://issues.apache.org/jira/browse/JAMES-4102
>             Project: James Server
>          Issue Type: Bug
>    Affects Versions: 3.8.3
>            Reporter: René Cordier
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> It's not possible to pull the zenko cloudserver S3 image anymore. I noticed a bunch of builds on the apache CI have been failing recently due to this:
> Caused by: java.lang.ExceptionInInitializerError: Exception org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=registry.scality.com/cloudserver/cloudserver:8.7.25, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@63c163e1) [in thread "main"]
> Trying locally I have the same issue.
> There is no documentation update or announcement on Zenko's side, I needed to do some archaeology on their backlog actually.
> Until I found this: [https://github.com/scality/cloudserver/pull/5557]
> Migrated from `registry.scality.com` to `ghcr.io`, which is github docker registry.
> Docker packages can be found here: [https://github.com/scality/cloudserver/pkgs/container/cloudserver%2Fcloudserver|https://github.com/scality/cloudserver/pkgs/container/cloudserver]
> The tags well... seem like random hash tags. So no idea which version of cloudserver it is.
> I guess we can try to upgrade to latest tag and see... Not convenient though, at all.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.