# Shell scripting inside Docker Compose? **URL:** \ **Category:** Enterprise\ **Created:** [February 28, 2020, 1:27pm UTC](https://travis-ci.community/t/shell-scripting-inside-docker-compose/7395 "2020-02-28T13:27:57Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\ **Post date:** [February 28, 2020, 1:36pm UTC](https://travis-ci.community/t/shell-scripting-inside-docker-compose/7395/2 "2020-02-28T13:36:10Z")
Hello again @Eclipse, Your script isn’t working because Alpine base images don’t have GNU bash. Seems like you’re running your bash script prematurely. I’ve seen a topic like this similar before. In the context of a CI system, it is extremely important to remove the `volumes:` line that mounts a local directory over your container’s `/app` directory: in the build instructions, you can see why it would cause problems specifically in Docker Compose. In a real world environment (and say not like a school) I’d personally suggest running both of these tools in a non-Docker environment. Via the Docker syntax you can ideally setup your unit tests without hard-to-setup context like a database container as well. FYI: I’d also run further tests based on network calls into the container. -Montana --- _[View the full topic](https://travis-ci.community/t/shell-scripting-inside-docker-compose/7395)._