c 'echo 'foo is $FOO' & echo 'bar is $BAR'' This runs instead of the image's entrypoint (if you want the image's entrypoint you have to run it yourself), and the syntax is awkward: # Run a shell command instead of the entrypoint If you really can't do this, you can override the docker run -entrypoint. Sh -c 'echo 'foo is $FOO' & echo 'bar is $BAR'' # Assuming the image correctly honors the CMD In the wrapper-script case, your alternate command will be run as the exec command, so all of the first-time setup will be done first. This will replace the CMD but leave the ENTRYPOINT intact. If you do these things, then you can use your initial docker run form. Specify which container to run the jobs in. With docker-compose I want to create a new container with new entrypoint: version: ‘2’ services: Joomla: image: joomla:joomla containername: Joomla ports: - 900:80 command: sh -c /start. Entrypoint sets the command and parameters that will be executed first when a container is run. Do this by choosing the Docker executor during registration. For this I commited my container to new image. ENTRYPOINT 'dotnet', 'applicationStartingPoint.dll' However, I need to have a shell script execute in the container before the application begins. do first time setup, run database migrations, set variables. To run CI/CD jobs in a Docker container, you need to: Register a runner so that all jobs run in Docker containers. By default, the ENTRYPOINT in the DockerFile for an application is something like. If you need to do some initial setup and then launch the main command, make the ENTRYPOINT be a shell script that ends with the special instruction exec The CMD will be passed into it as parameters, and this line replaces the shell script with that command. If you only need to run one command with no initial setup, make it be the CMD and not the ENTRYPOINT: CMD. As a style point, this gets vastly easier if your image has a CMD that can be overridden.

Docker entrypoint