CircleCI Ideas

Remote Docker not unreachable from localhost

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Nov 29 2018
  • New
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    May 16, 2019 13:58

    I would like to share that this is also a blocker for everyone who would want to use TestContainers 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 10, 2019 17:11

    Yes - this is yet another reason for me to start moving my team away from CircleCI.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    07 Feb 14:26

    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.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    23 Feb 17:39

    +1 on wanting to use Testcontainers.