-
-
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
Problem with docker-compose #484
Comments
Hi @kronar, which credentials-store do you use in your Docker for Mac installation? Might be related to #483. |
Hi, @kiview |
I thought the problem resides at this point:
Could you provide the docker-compose.yml file? Does it work if you use |
@kiview the issue is already having enough info :) We might handle it in TC by ignoring the error from |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this. |
This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case. |
I am seeing this issue. I have a docker-compose with two services:
When running the test using: override val container = DockerComposeContainer(
new File(getClass.getResource("/docker-compose.yml").toURI),
exposedServices = Seq(ExposedService("myservice", 8080))) the postgres image is correctly pulled from the registry, but docker-compose fails Note that if I run docker-compose up from my shell everything works just fine.
|
This is related. Seems that older versions of |
@berardino Try to use |
Tried to write some integration test with TestContainers, I faced following issue
Produces the following output
It seems that it is not direct issue of TestContainers but looks similar to docker/compose#3660.
I've verified this on my machine and execution of
docker-compose pull
also fails because of docker login was never executed.Also, possibly some workaround required to be implemented.
Additional info:
OS: Mac OS 10.12.6
$ docker -v
Docker version 17.09.0-ce, build afdb6d4
$ docker-compose -v
docker-compose version 1.16.1, build 6d1ac21
$ docker-machine -v
docker-machine version 0.12.2, build 9371605
TestContainers v 1.4.3
The text was updated successfully, but these errors were encountered: