-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mirroring settings ignored since 1.15.0-rc1 #3352
Comments
@andrus are you referring to |
Yes |
Appears to be so. I take the same code, and change TC version in the pom.xml:
Perhaps 1.15.x added some explicit calls to the registry? |
Ok, found it! A colleague from the ops team pointed to this change - switch to "testcontainers" prefix from "testcontainersofficial". Turns out our repo proxy had explicit prefix matching for images to avoid untrusted sources. Changed that, and everything works. Perhaps something to mention in the upgrade notes. |
@andrus thanks for reporting back! I am glad that it works well now :) We indeed had a bit of back and forth with the Docker Hub orgs, but it is in the release notes: |
Thanks for awesome support BTW! |
Environment: Bamboo CI, Linux, Java 11, Docker 19.03.13. DockerHub is blocked on the CI agent network, and instead mirroring is setup to use a local registry.
Have a build that worked fine on TC "1.14.3". Upgraded to "1.15.0-rc2" to address MacOS build issue (#3166), and the builds started failing. Same failure on either "1.15.0-rc1" or "1.15.0-rc2". Looks like the new version attempts to connect to "registry-1.docker.io" despite mirroring settings, and predictably fails (see above).
Good build (1.14.3)
Failing build (1.15.0-rc*):
The text was updated successfully, but these errors were encountered: