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/cli/reference.mdx
+2-2
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ A variety of Depot CLI calls accept a `--token` flag, which allows you to specif
41
41
42
42
The `bake` command allows you to define all of your build targets in a central file, either HCL, JSON, or Compose. You can then pass that file to the `bake` command and Depot will build all of the target images with all of their options (i.e. platforms, tags, build arguments, etc.).
43
43
44
-
By default, `depot bake` will leave the built image in the remote builder cache. If you would like to download the image to your local Docker daemon (for instance, to `docker run` the result), you can use the `--load` flag.
44
+
By default, `depot bake` will leave the built image in the remote builder cache. If you would like to download the image to your local Docker daemon (for instance, to `docker run` the result), you can use the `--load` flag. In some cases it is more efficient to load from the registry, so this may result in the build getting saved to the Depot Registry.
45
45
46
46
Alternatively, to push the image to a remote registry directly from the builder instance, you can use the `--push` flag.
47
47
@@ -176,7 +176,7 @@ This command accepts all the command line flags as Docker's `docker buildx bake`
176
176
177
177
Runs a Docker build using Depot's remote builder infrastructure.
178
178
179
-
By default, `depot build` will leave the built image in the remote builder cache. If you would like to download the image to your local Docker daemon (for instance, to `docker run` the result), you can use the `--load` flag.
179
+
By default, `depot build` will leave the built image in the remote builder cache. If you would like to download the image to your local Docker daemon (for instance, to `docker run` the result), you can use the `--load` flag. In some cases it is more efficient to load from the registry, so this may result in the build getting saved to the Depot Registry.
180
180
181
181
Alternatively, to push the image to a remote registry directly from the builder instance, you can use the `--push` flag.
**Note**: Windows runners don't come equipped with Hyper-v because of an AWS limitation on EC2. Therefore, if you use things that require it like `docker`, than Depot Windows Runners are unlikely to work for you.
0 commit comments