Migrate from Docker-Hub to EF-hosted Docker-Image registry

[HannesWell]

Docker-Hub will change it's usage limits with effect from 1 April, which is next week: https://docs.docker.com/docker-hub/usage/

Starting April 1, 2025, all users with a Pro, Team, or Business subscription will have unlimited Docker Hub pulls with fair use.
Unauthenticated users and users with a free Personal account have the following pull limits:
    Unauthenticated users: 10 pulls/hour
    Authenticated users with a free account: 100 pulls/hour

Currently we use custom Docker-Images hosted at Docker-Hub to build the native binaries for SWT and Equinox and for Smoke-Tests:

• https://github.com/eclipse-platform/eclipse.platform.swt/blob/e4fc88a6705c0d82e7b08f2c314bae90aef02b4c/Jenkinsfile#L22-L27
• https://github.com/eclipse-equinox/equinox/blob/7bdfa2ad418b14fdc9cbca7b15d6f7b6a8ee31c6/Jenkinsfile#L20
• https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/9732bb9cb7024a08fa578adb5ebbbcc5d4b8e167/JenkinsJobs/SmokeTests/StartSmokeTests.jenkinsfile#L35-L41

@fredg02 or @heurtematte can you clarify how we will be affected by this change? Especially does our usage in the EF-hosted Jenkins is considered as unauthenticated use and thus affected by the 10 pulls per hour limit? Since this is counted per IP, I fear that it would not be sufficient, not even if we are authenticated.

I remember your mail from October last year: https://www.eclipse.org/lists/cross-project-issues-dev/msg19963.html Is this still up to date? And would it make sense to migrate to the EF-hosted Docker registry now respectively is it already ready? If yes, what do we have to change in the consuming jobs listed above and in our [docker-image build job?

• https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/9732bb9cb7024a08fa578adb5ebbbcc5d4b8e167/JenkinsJobs/Builds/DockerImagesBuild.jenkinsfile

[fredg02]

@fredg02 or @heurtematte can you clarify how we will be affected by this change?

Our build cluster is utilizing a paid Docker Hub account to pull Docker images, and therefore our pull limits are a lot higher. So project builds should not be affected by this change.

And would it make sense to migrate to the EF-hosted Docker registry now respectively is it already ready?

We are still evaluating the usage of Nexus 3 as a Docker registry. We are currently blocked by an issue to test this for internal Docker images. Once this is fixed and tested, there is still a big question about the feasibility of hosting Docker images of Eclipse projects, especially wrt to the retention policy.

[HannesWell]

@fredg02 or @heurtematte can you clarify how we will be affected by this change?

Our build cluster is utilizing a paid Docker Hub account to pull Docker images, and therefore our pull limits are a lot higher. So project builds should not be affected by this change.

Thank you for the clarification. Then we don't have to worry about that.

And would it make sense to migrate to the EF-hosted Docker registry now respectively is it already ready?

We are still evaluating the usage of Nexus 3 as a Docker registry. We are currently blocked by an issue to test this for internal Docker images. Once this is fixed and tested, there is still a big question about the feasibility of hosting Docker images of Eclipse projects, especially wrt to the retention policy.

Understand. Then I suggest to keep this issue open until a migration is possible and we can decide to do it or it's clear that it won't be possible.

[fredg02]

Understand. Then I suggest to keep this issue open until a migration is possible and we can decide to do it or it's clear that it won't be possible.

Please keep in mind that we are tracking the effort in the help desk issue. I probably won't remember to update this GitHub issue.

[HannesWell]

Understand. Then I suggest to keep this issue open until a migration is possible and we can decide to do it or it's clear that it won't be possible.

Please keep in mind that we are tracking the effort in the help desk issue. I probably won't remember to update this GitHub issue.

Yes of course and I'm subscribed to that issue. I intended this issue for tracking on this project's side.