You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
would it be possible to prepend "library/" to the official alpine docker image pulled in ("library/alpine"); that’s where the image is actually located.
Reason: it is often desired to use a dockerhub mirror (because of rate limits), which we achieve by setting the following property: "hub.image.name.prefix=our.company.mirror/". While this works fine for the testcontainers images, it doesn’t work for the official docker images like "alpine". We have to work around that by setting the property "tinyimage.container.image=library/alpine:3.16", which is deprecated and discouraged according to the docs.
The text was updated successfully, but these errors were encountered:
It is perfectly fine for us to use the asCompatibleSubstituteFor workaround when instantiating e.g. postgres containers in our code. The "alpine" image is not actively used by ourselves though; it is implicitly used by the testcontainers framework. Since we don’t have control over this one, we have to use the deprecated property tinyimage.container.image.
akurth
changed the title
[Enhancement]: Prepend library/ to docker official images
[Enhancement]: Prepend "library/" to official docker image "alpine"
Nov 14, 2022
Module
Core
Proposal
Hello,
would it be possible to prepend "library/" to the official alpine docker image pulled in ("library/alpine"); that’s where the image is actually located.
Reason: it is often desired to use a dockerhub mirror (because of rate limits), which we achieve by setting the following property: "hub.image.name.prefix=our.company.mirror/". While this works fine for the testcontainers images, it doesn’t work for the official docker images like "alpine". We have to work around that by setting the property "tinyimage.container.image=library/alpine:3.16", which is deprecated and discouraged according to the docs.
The text was updated successfully, but these errors were encountered: