Skip to content

Commit 9fc64fd

Browse files
authored
Add entrypoint (#94)
* Add entrypoint * entrypoint can be empty
1 parent 64480fb commit 9fc64fd

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

content/en/docs/measuring/usage-scenario.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,10 @@ services:
125125
+ Defaults to `/tmp/repo`
126126
- `command:` **[str]** *(optional)*
127127
+ Command to be executed when container is started. When container does not have a daemon running typically a shell is started here to have the container running like `bash` or `sh`.
128+
- `entrypoint:` **[str]** *(optional)*
129+
+ Declares the default entrypoint for the service container. This overrides the ENTRYPOINT instruction from the service's Dockerfile.
130+
+ The value of `entrypoint` can either be an empty string (ENTRYPOINT instruction will be ignored) or a single word (helpful to provide a script).
131+
+ If you need an entrypoint that consists of multiple commands/arguments, either provide a script (e.g. `entrypoint.sh`) or set it to an empty string and provide your commands via `command`.
128132
- `shell:` **[str]** *(optional)*
129133
+ Will execute the `setup-commands` in a shell. Use this if you need shell-mechanics like redirection `>` or chaining `&&`.
130134
+ Please use a string for a shell command here like `sh`, `bash`, `ash` etc. The shell must be available in your container

0 commit comments

Comments
 (0)