gcloud beta compute instances attach-disk - attach a disk to an instance

gcloud beta compute instances attach-diskINSTANCE_NAME--disk=DISK[--boot][--csek-key-file=FILE][--device-name=DEVICE_NAME][--disk-scope=DISK_SCOPE; default="zonal"][--force-attach][--interface=INTERFACE][--mode=MODE; default="rw"][--zone=ZONE][GCLOUD_WIDE_FLAG …]

gcloudcomputeinstancesattach-diskexample-instance--diskDISK--zoneus-central1-a

attaches the disk named 'DISK' to the instance named 'example-instance' in zoneus-central1-a.

After you create and attach a new disk to an instance, you mustformatand mount the disk so that the operating system can use the availablestorage space. You can attach an existing non-boot disk to more than oneinstance. For more information, seeShare a diskbetween VMs.

gcloudbetacomputeinstancesattach-diskmy-instance--disk=my-disk--boot

To attach a device named 'my-device' for read-only access to an instance named'my-instance', run:

gcloudbetacomputeinstancesattach-diskmy-instance--device-name=my-device--mode=ro

INSTANCE_NAME

Name of the instance to operate on. For details on valid instance names, referto the criteria documented under the field 'name' at:https://cloud.google.com/compute/docs/reference/rest/v1/instances

--disk=DISK

The name of the disk to attach to the instance.

--boot

Attach the disk to the instance as a boot disk.

--csek-key-file=FILE

Path to a Customer-Supplied Encryption Key (CSEK) key file that maps ComputeEngine resources to user managed keys to be used when creating, mounting, ortaking snapshots of disks.

If you pass- as value of the flag, the CSEK is read from stdin.Seehttps://cloud.google.com/compute/docs/disks/customer-supplied-encryptionfor more details.

--device-name=DEVICE_NAME

An optional name that indicates the disk name the guest operating system willsee. (Note: Device name does not correspond to mounted volume name). Must matchthe disk name if the disk is going to be mounted to a container with--container-mount-disk (alpha feature).

--disk-scope=DISK_SCOPE; default="zonal"

The scope of the disk.DISK_SCOPE must be one of:

regional

The disk specified in --disk is interpreted as a regional disk in the sameregion as the instance. Ignored if a full URI is provided to the--disk flag.

zonal

The disk specified in --disk is interpreted as a zonal disk in the same zone asthe instance. Ignored if a full URI is provided to the--disk flag.

--force-attach

Attach the disk to the instance even if it is currently attached to anotherinstance. The attachment will succeed even if detaching from the previousinstance fails at first. The server will continue trying to detach the disk fromthe previous instance in the background.

--interface=INTERFACE

The interface of the disk.INTERFACE must be one of:

NVME

NVME

SCSI

SCSI

--mode=MODE; default="rw"

Specifies the mode of the disk.MODE must be one of:

ro

Read-only.

rw

Read-write.

--zone=ZONE

Zone of the instance to operate on. If not specified, you might be prompted toselect a zone (interactive mode only).gcloud attempts to identify theappropriate zone by searching for resources in your currently active project. Ifthe zone cannot be determined,gcloud prompts you for a selection withall available Google Cloud Platform zones.

To avoid prompting when this flag is omitted, the user can set thecompute/zone property:

gcloudconfigsetcompute/zoneZONE

A list of zones can be fetched by running:

gcloudcomputezoneslist

To unset the property, run:

gcloudconfigunsetcompute/zone

Alternatively, the zone can be stored in the environment variableCLOUDSDK_COMPUTE_ZONE.

Run$gcloud help for details.