How to connect to the TEAMCITY_DOCKER_NETWORK from a script step

Docker Engine General
1

TeamCity + Docker question here. I’ve got TeamCity running a docker-compose.yml and it tells me that it has created a network: Creating network "full-stack_default" with the default driver. One of the containers in the compose serves a web app on port 8080.

In another TeamCity build step I have a script step (note it’s not a dockerCompose like in the paragraph above) that attempts to hit the web app using the URL http://full-stack_default:8080 but it cannot be found.

Any suggestions for how to connect to the TeamCity docker network?

2

I would recommend to share you used compose file(s).

3

I can… but they just look like basic compose files. I’m not using the networks keys at this point. I’ve tried many variations of them but they seem to have no effect.

I really need assistance from someone who’s used Docker in TeamCity, because I believe this is related to how TeamCity created a network within a dockerCompose step and having another step access that network. Do I need to put everything in the same docker-compose.yml file or is it possible to have one for my full stack application, and have my test runner be in a script step? Given that TeamCity is already running in a Docker container, shouldn’t it have access to the network?

4

Then you are probably better served at a TeamCity forum, like teamcity-support.