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: README.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,8 @@ The name of the service the command should be run within. If the docker-compose
33
33
34
34
A list of services to push. You can specify just the service name to push or the format `service:registry:tag` to override where the service's image is pushed to. Needless to say, the image for the service must have been built in the very same step or built and pushed previously to ensure it is available for pushing.
35
35
36
+
**Important**: when the image for a service is pushed it sets metadata on the build so that future steps will know to use that image to run that service. This can lead to race conditions when pushing multiple images for a service. Can be turned off with the `push-metadata` option.
37
+
36
38
:warning: If a service does not have an `image` configuration and no registry/tag are specified in the `push` option, pushing of the service will be skipped by docker.
37
39
38
40
:warning: The `push` command will fail when the image refers to a remote registry that requires a login and the agent has not been authenticated for it (for example, using the [ecr](https://github.com/buildkite-plugins/ecr-buildkite-plugin) or [docker-login](https://github.com/buildkite-plugins/docker-login-buildkite-plugin) plugins).
@@ -171,6 +173,12 @@ Default: `false`
171
173
172
174
A number of times to retry failed docker pull. Defaults to 0.
173
175
176
+
#### `push-metadata` (push only, boolean)
177
+
178
+
Whether to set the metadata aboout the image for a service being pushed.
179
+
180
+
Default: `true`.
181
+
174
182
#### `push-retries` (push only, integer)
175
183
176
184
A number of times to retry failed docker push. Defaults to 0.
@@ -322,11 +330,11 @@ Note that [the effect of this option changes depending on your docker compose CL
322
330
323
331
#### `entrypoint` (run only)
324
332
325
-
Sets the `--entrypoint` argument when running `docker compose`.
333
+
Sets the `--entrypoint` argument when running `docker compose`, can be set to an empty string.
326
334
327
335
#### `require-prebuild` (run only, boolean)
328
336
329
-
If no prebuilt image is found for the run step, it will cause the plugin to fail the step.
337
+
Make sure that images for the service being run and all specified in `pull` are found for the run step, fail the step otherwise. Note that specifying a `run-image` will skip this check for the service being run.
Copy file name to clipboardExpand all lines: docs/examples.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,7 @@ steps:
26
26
27
27
The plugin will honor the value of the `COMPOSE_FILE` environment variable if one exists (for example, at the pipeline or step level). But you can also specify custom Docker Compose config files with the `config` option:
0 commit comments