testcontainers / testcontainers/testcontainers-java
TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX with docker-compose.yml
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Hi,
I am using a docker-compose.yml for my tests:
version: '3.4'
services:
elastic:
image: elasticsearch:7.9.2
[...]
and try to use a private docker registry when running the tests:
export TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX=<my registry>
./gradlew clean test
Nevertheless, it seems that my default registry is not picked up for the images defined in docker-compose.yml (but it is for the ones used internally by testcontainer such as testcontainers/ryuk.
I went to this conclusion by checking docker image ls which doesn't return the images prefixed by the private registry.
Do I miss something or does TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX not work with docker-compose.yaml?
I'm using org.testcontainers:testcontainers:1.15.3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report with the shown docker-compose.yml, TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX, Gradle, and Testcontainers 1.15.3, then inspect docker image ls and the compose-related implementation. Done when the behavior is corrected for compose-defined images or the limitation is documented with appropriate test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, java
- Domain
- devops, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100