This sounds like a Docker networking problem. I would think you need to have docker-compose and bring your microservice and all the dependencies up and then tes

This sounds like a Docker networking problem. I would think you need to have docker-compose and bring your microservice and all the dependencies up and then test against your microservice _in the same network_. I've written some .gitlab-ci.yml files in the last months. What I do is using a script to validate against the Gitlab lint API. This is done every time I save the file. I also run gitlab-runner on my local machine and test my jobs with `gitlab-runner exec docker`. Don't forget to commit what you need in the job. You don't need to commit the .gitlab-ci.yml, but everything else, because the first step to run the job is cloning the repo. I have also updated the brew formulas for the last releases of gitlab-runner. Gitlab is great software and I've worked with it and administrated it for the last 5 years. I don't want to miss it.