![how to curl auth with docker ip how to curl auth with docker ip](https://www.tecmint.com/wp-content/uploads/2018/08/Download-File-Using-Curl-Command.png)
Thanks for your help! It turns out the issue was actually with my volume command in the docker-compose file, which was looking for a volume that doesn’t exist on the GitHub Actions VM. This docker-compose file works great locally but something seems to be amiss when running on GitHub actions. Note that the web service is not running: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĭ56c857f7316 postgres "docker-entrypoint.s…" About a minute ago Up About a minute 0.0.0.0:5432->5432/tcp postgresĪnd the output of the test step is: Error response from daemon: Container c9e106fab289d59c8fd233544cc7a642412f315241981bf3e00edba0a6a186eb is not running The output of the “docker ps” call is below. Note that I added the 60s wait time, because I thought the test suite was running before the container could stand up but it didn’t seem to help. Run: docker exec backend pytest -skip-auth
![how to curl auth with docker ip how to curl auth with docker ip](https://media.springernature.com/original/springer-static/image/chp%3A10.1007%2F978-1-4842-1830-3_13/MediaObjects/978-1-4842-1830-3_13_Fig1_HTML.jpg)
uses: name: Build the docker-compose stack DJANGO_SETTINGS_MODULE=$ĭJANGO_SETTINGS_MODULE: app_ My docker-compose.yml file is version: '3' I am running a django webapp in one container and postgres in another and tying the two with docker-compose.
![how to curl auth with docker ip how to curl auth with docker ip](https://i.stack.imgur.com/RVIjy.jpg)
I am trying to use GitHub actions to automate my test pipeline, but cannot seem to get the containers to run in order to test them.