Remote Docker not unreachable from localhost
closed
G
Giovanni Toraldo
The unique reason to prevent me to go with docker executor is that during the build I can't build a new image and execute tests against it, since containers running with setup_remote_docker aren't directly accessible from localhost.
CCI-I-712
Liya Ai
closed
Closed per comment from 8/2020 - please comment if there are further questions.
Liya Ai
Hi everyone! Our recommendation if you want to run tests on the same host as where the Docker containers are running is to use the Machine executor. Please let us know if there are any further questions or concerns.
A
Alex Kuz
Any updates? More and more people are starting to use test containers and this is a show stopper for using circle ci.
L
Luis Miguel Mejía-Suárez
Any new about this? Most of our projects are starting to have some tests using testcontainers for checking the correctness of our queries against a real DB without needing to deploy the code into a development environment. We probably will be migrating out of CircleCI on a short term if we can no longer use the docker executor.
C
Corey Fritz
+1 on wanting to use Testcontainers.
R
Ryan Morrisey
In the same boat as guest from May 16th. Would really like to be able to use TestContainers without needing to use a machine executor. If machine executor prices go up as foreshadowed by the docs "Note: Using machine may require additional fees in a future pricing update.", we will definitely have to reevaluate our CI options.
B
Barry o'neill
Yes - this is yet another reason for me to start moving my team away from CircleCI.
L
Luis Miguel Mejía-Suárez
I would like to share that this is also a blocker for everyone who would want to use TestContainers