/v2/microvms/{microvm_id}/execRun a command in a MicroVM
To run a command in a MicroVM's workload container, send a POST request to
/v2/microvms/{microvm_id}/exec.
argv runs directly, not through a shell, with standard input closed. If the MicroVM is
paused and auto-resume is on, the request resumes it and waits until it is running.
A command has 60 seconds to finish. Your team can run 32 commands at once and 60 commands per minute. Rejected requests count toward the per-minute limit.
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
3 documented failures
INVALID_SIZEno supported size matches the requested resources: 3 vCPU with 2048 MiB of memory (supported: 1vCPU/2048MiB, 2vCPU/4096MiB, 8vCPU/16384MiB, 16vCPU/32768MiB)
INVALID_AUTO_PAUSEauto_pause.enabled cannot be false; omit it to keep the 5 minute default, or set idle_timeout up to the account maximum
FAILED_PRECONDITIONcheckpoint 01a11cd5-25dd-790f-a77c-3677f24bca85 is still being captured; retry delete once the capture completes
One documented failure
PERMISSION_DENIEDpermission denied
One documented failure
NOT_FOUNDMicroVM not found
One documented failure
UNAVAILABLEworkload unavailable
A 400 is returned: The request was malformed, failed validation, or is not allowed in the resource's current state. A 401 is returned: Authentication failed due to invalid credentials. A 403 is returned: The token does not have the required scope, or your team has reached a limit. A 404 is returned: The MicroVM or checkpoint does not exist, or it belongs to another team. A 429 is returned: The API rate limit has been exceeded. A 500 is returned: There was a server error. A 502 is returned: The command did not reach the workload, for example because the container is not running. Any other status is an error: There was an unexpected error.