Hi,

We want to streamline the boot of our docker image and have inserted a startup.sh file on our docker image that at startup time launches services like REDIS / MONGODB and APACHE.

As far as we can now see the problem is that startup.sh is never executed since pipelines create an ENTRYPOINT and bash file for the compiled bitbucket-pipeline.yml instructions and then executes this bash file when starting the container.

MongoDB can then only be executed via a --fork, as a service. So it will not freeze the bash script. It works.. but booting up a docker container then takes an extra 5 minutes before other bash commands can be executed.

Its a working work around.. but is it possible that the CMD in the docker container is executed first? Or does that create more problems on your end?

Kind regards,

Gerhard Richard Edens