Skip to content

Commit d5c8683

Browse files
Michal-Matousekib-steffen
authored andcommitted
[documentation] container run command is ignored when build_only=true (#229)
1 parent a472af4 commit d5c8683

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/job/docker.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The job type docker is one of the most important jobs. You can use it to run any
3030
|type|true|string||Has to be "docker" to run a single Docker container|
3131
|name|true|string||Name of the job|
3232
|docker_file|true|string||Path to the `Dockerfile`|
33-
|command|false|string||The command in [exec form](https://docs.docker.com/engine/reference/builder/#cmd) to be used when the container is run. Ignored if `build_only=false`|
33+
|command|false|string||The command in [exec form](https://docs.docker.com/engine/reference/builder/#cmd) to be used when the container is run. Ignored if `build_only=true`|
3434
|resources|true|[Resource Configuration](/docs/job/resources.md)||Specify the required resources for your job.|
3535
|build_only|true|boolean|true|If set to true the container will only be build but not run. Use it if you only want to build a container and push it to a registry. See here for how to push to a docker registry.|
3636
|build_context|false|string||Specify the docker build context. If not set the directory containing the `infrabox.json` file will be used.|

0 commit comments

Comments
 (0)