You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/measuring/usage-scenario.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,10 @@ services:
125
125
+ Defaults to `/tmp/repo`
126
126
- `command:`**[str]** *(optional)*
127
127
+ 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`.
128
132
- `shell:`**[str]** *(optional)*
129
133
+ Will execute the `setup-commands` in a shell. Use this if you need shell-mechanics like redirection `>` or chaining `&&`.
130
134
+ 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