Skip to content

Commit

Permalink
Remove wrong mention of extra arguments to build backend (#93)
Browse files Browse the repository at this point in the history
  • Loading branch information
MrHedmad authored Apr 15, 2024
2 parents 7e47e8d + 5a467ea commit 8e5fedd
Showing 1 changed file with 0 additions and 19 deletions.
19 changes: 0 additions & 19 deletions docs/src/tutorial/run.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,22 +147,3 @@ For example, you can tell `make` to build a different target with this syntax:
kerblam run make_pipeline -- other_target
```
As if you had run `make other_target` yourself.

Note that these extra arguments are passed to the `docker` or `podman` command
for pipelines that have available dockerfiles.
This means that you can communicate to the `docker`/`podman` process with this,
for example to set limits on the resources the docker container is using.
```bash
kerblam run my_dockerized_pipeline -- --cpu-shares=3 -m 4G
```
Note that all ending arguments are transparently passed by the `docker` or
`podman` instance to the underlying entrypoint, so non-container-specific
arguments can be passed easily to the underlying `make` or `bash` process.
To force `docker` to just pass the arguments to the underlying entrypoint,
you can use the odd syntax of:
```bash
kerblam run my_pipe -- -- arg_1 arg_2 ...
```
The first `--` is "eaten up" by Kerblam!, and the second one is passed to the
containerization engine, telling it to pass `arg_1`, `arg_2` etc... as-is to
the entrypoint.

0 comments on commit 8e5fedd

Please sign in to comment.