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: docs/code.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,7 @@ container in order to run:
8
8
* --image "Docker image"
9
9
* --input "path to file in cloud storage"
10
10
* --input-recursive "path to directory in cloud storage"
11
+
* --boot-disk-image "Custom boot disk image to use"
11
12
12
13
The following explains each option and how to choose which to use.
13
14
@@ -231,3 +232,12 @@ chmod u+x ${SCRIPT_DIR}/*.sh
231
232
${SCRIPT_DIR}/script1.sh
232
233
${SCRIPT_DIR}/script2.sh
233
234
```
235
+
236
+
## --boot-disk-image "Custom boot disk image to use"
237
+
238
+
For most uses, the underlying virtual machine image is transparent to your tasks; the provider default is sufficient. However, there are cases where you may want to specify a custom boot disk image.
239
+
240
+
When using GPU accelerators, an image with GPU drivers is needed. The `google-batch` provider will automatically select the `batch-debian` image when `--accelerator-type` and `--accelerator-count` are specified.
241
+
242
+
If your `dsub` task does not have internet access, it may fail as this image will attempt to update the GPU drivers. You may instead pre-build a custom image with the drivers installed, specify it with the `--boot-disk-image`, and set '--install-gpu-drivers' to `false`
243
+
Specifically for the `google-batch` provider, information about available images can be found [here](https://cloud.google.com/batch/docs/view-os-images)
0 commit comments