cloud-init1
Cloud instance initialization
Usage
cloud-init [-h]
[-d]
[--force]
[-v]
[SUBCOMMAND]
Overview
Cloud-init provides a mechanism for cloud instance initialization. This is done by identifying the cloud platform that is in use, reading cloud meta-data, vendor-data and user-data, and then initializing the instance as requested.
Options
-
-h, --help -
Show help message and exit.
-
-v, --version -
Show program's version number and exit.
-
--all-stages -
INTERNAL: Run cloud-init's stages under a single process using a synchronization protocol. This is not intended for CLI usage.
Subcommands
Please see the help output for each subcommand for additional details, flags, and subcommands.
|
Analyze cloud-init logs and data. |
|---|---|
|
Collect and tar all cloud-init debug info. |
|
Remove logs and artifacts so cloud-init can re-run. |
|
Run development tools. See help output for subcommand details. |
|
List defined features. |
|
Query standardized instance metadata from the command line. |
|
Validate cloud-config files using jsonschema. |
|
Manually run a single module. Useful for testing during development. |
|
Report cloud-init status or wait on completion. |
Deprecated
-d, --debug
|
Show additional pre-action logging (default: False). |
|---|---|
|
Force running even if no datasource is found (use at your own risk). |
|
Initialize cloud-init and execute initial modules. |
|
Activate modules using a given configuration key. |
Exit status
|
0 - Success |
|
|
1 - Error - Cloud-init failed. |
|
|
2 - Recoverable error - Cloud-init completed but experienced errors. |
Releases
4 releases since Debian 11 (Bullseye); the text changed 2 times.
--all-stages since Debian 13 (Trixie).
--debug until Debian 12 (Bookworm);
--files until Debian 12 (Bookworm);
--force until Debian 12 (Bookworm);
-d until Debian 12 (Bookworm);
-f until Debian 12 (Bookworm).