Skip to content
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.

Sign up for GitHub

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

Jump to bottom

add more information for using registry mirror #2477

Merged
merged 1 commit into from Apr 11, 2020
Merged

add more information for using registry mirror #2477

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/features/configuration.md
View file
Open in desktop
Expand Up @@ -48,6 +48,11 @@ Some companies disallow the usage of Docker Hub, but you can override `*.image`
Another possibility is to set up a registry mirror in your environment so that all images are pulled from there and not directly from Docker Hub.
For more information, see the [official Docker documentation about "Registry as a pull through cache"](https://docs.docker.com/registry/recipes/mirror/).

!!!tip
Registry mirror currently only works for Docker images with image name that has no registry specified (for example, for Docker image `mariadb:10.3.6`, it works, for Docker image `quay.io/testcontainers/ryuk:0.2.3`, not).
Workaround is to to configure the affected Docker image in `.testcontainers.properties`.
For example: `ryuk.container.image = testcontainers/ryuk:0.2.3` or `ryuk.container.image = <your.docker.registry>/testcontainers/ryuk:0.2.3`

## Customizing Ryuk resource reaper

> **ryuk.container.image = quay.io/testcontainers/ryuk:0.2.3**
Expand Down