With the release of tox-docker 5.0.0, tox has stopped working for us because: "This directive (ports) was removed in tox-docker version 5.0. Use expose instead. The ability to map a container port to a specific host port was completely removed."
I have asked a question about forming MONGO_CONNSTRING in tox-docker's issue tracker. The suggestion I received was to use a wrapper script. I prefer breaking down MONGODB_CONNSTRING to component parts and using MONGO_PORT variable set by tox-docker to figure out the exposed port. That feels cleaner, and consistent with our usage of MQ_HOST and MQ_PORT.
With the release of tox-docker 5.0.0, tox has stopped working for us because: "This directive (
ports) was removed in tox-docker version 5.0. Useexposeinstead. The ability to map a container port to a specific host port was completely removed."I have asked a question about forming
MONGO_CONNSTRINGin tox-docker's issue tracker. The suggestion I received was to use a wrapper script. I prefer breaking downMONGODB_CONNSTRINGto component parts and usingMONGO_PORTvariable set by tox-docker to figure out the exposed port. That feels cleaner, and consistent with our usage ofMQ_HOSTandMQ_PORT.