This article is about CodeShip Pro.

jet run

You will need about one minute to read this article.


Run a command inside a service container.


jet run SERVICE [COMMAND [ARGS...]] [flags]


Name, shorthand Default Description
--debug Turn debug output on
--dir current directory The directory to use
--dockercfg-service The name of the service with which the dockercfg should be generated
--encrypted-dockercfg-path The path to the encrypted dockercfg file to be used
--entrypoint Override the entrypoint of the image
--env, -e Set an environment variable (can be used multiple times)
--key-path codeship.aes The key path for encrypting secure environment variables.
--no-remove Do not remove any containers that are run, overrides all other settings
--no-tty, -T Disable pseudo-tty allocation
--pull-if-present false Pull images that are already present
--services-path codeship-services.yml The relative services path

Extended description

The jet run command will build and execute a service from the codeship-services.yml file, or run a single command.

This is a good way to debug your services

For instance, you can run jet run service_app or jet run service_app echo "hello" where service_app is one of the services defined in your codeship-services.yml.


Debugging a Build

You can debug your builds locally by first executing jet run, then connect to your running containers to manually run the commands from your codeship-steps.yml file.

As an example, the following will start your service, display the container ID, and then connect to the running container using the container ID.

$ docker ps -a
$ docker exec -it CONTAINER_ID /bin/sh

Need more help?

Contact our support team or post on Stack Overflow using the tag #codeship. Did you check the status page and changelog?

There are also several code examples and sample projects available for you to get started with.

Article not helpful?

Does this article need improvement? If so, please send feedback or submit a pull request!