CLOUD-INIT(1)
β¨ NAME β¨
okay so cloud-init (that's the manual page for it, the CLOUD-INIT(1) one π) is the thing that does cloud instance initialization π§
πΈ Quick note on the header
The page is from the General Commands Manual, and the manual name is CLOUD-INIT(1). Iconic. π
π SYNOPSIS π
cloud-init [-h] [-d] [--force] [-v] [SUBCOMMAND]
π¦ DESCRIPTION π¦
okay so Cloud-init gives you a mechanism for cloud instance initialization, and it's giving main character energy β¨ It works by figuring out which cloud platform you're on, reading the cloud meta-data, vendor-data and user-data, and then initializing the instance however you asked. literally so smart π§ π
π OPTIONS π
-h,--helpβ shows the help message and exits. bestie, always start here π«Ά-v,--versionβ shows the program's version number and exits π₯--all-stagesβ INTERNAL π this runs cloud-init's stages under a single process using a synchronization protocol. it's not meant for CLI usage, so please don't go poking at it π
π SUBCOMMANDS π
please check the help output for each subcommand for extra details, flags, and subcommands, periodt π
analyzeβ analyzes cloud-init logs and data πcollect-logsβ collects and tars all cloud-init debug info π¦cleanβ removes logs and artifacts so cloud-init can re-run π§Ήdevelβ runs development tools. see the help output for subcommand details π οΈfeaturesβ lists defined features β¨queryβ queries standardized instance metadata from the command line πschemaβ validates cloud-config files using jsonschema πsingleβ manually runs a single module. useful for testing during development π§ͺstatusβ reports cloud-init status or waits on completion β³
π DEPRECATED π
these ones are deprecated, so no cap, don't build your whole vibe on them π
-d,--debugβ shows additional pre-action logging (default:False) π--forceβ forces running even if no datasource is found. use at your own risk π¬initβ initializes cloud-init and executes initial modules πmodulesβ activates modules using a given configuration key ποΈ
π EXIT STATUS π
okay so here's how it tells you how things went:
0β Success! π1β Error. cloud-init failed π2β Recoverable error. cloud-init completed but ran into errors π₯²
π«§ COPYRIGHT π«§
Copyright (C) 2020 Canonical Ltd. License GPL-3 or Apache-2.0 βοΈ
π SEE ALSO π
the full documentation lives at <https://docs.cloud-init.io> π
bestie, this page is from CLOUD-INIT(1) in the General Commands Manual, and it's the version from the cloud-init source line πΈ Last updated... the page itself has the date, go check it, I'm not guessing π love you, mwah π«Άβ¨
π¦ where this page comes from
- alpine 3.24: cloud-init-doc 26.1-r3 Β· Apache-2.0 OR GPL-3.0-only
- arch rolling: cloud-init 26.2-1 Β· GPL-3.0-only OR Apache-2.0
- fedora 44: cloud-init 26.1-1.fc44 Β· Apache-2.0 OR GPL-3.0-only
- ubuntu jammy: cloud-init 26.1-0ubuntu1~22.04.1 Β· GPL-3.0-only OR Apache-2.0
- ubuntu noble: cloud-init 26.1-0ubuntu1~24.04.1
- ubuntu noble: cloud-init 26.2-0ubuntu1~24.04.2 Β· GPL-3.0-only OR Apache-2.0
- ubuntu questing: cloud-init-base 26.1-0ubuntu1~25.10.1 Β· GPL-3.0-only OR Apache-2.0
- ubuntu resolute: cloud-init-base 26.1-0ubuntu2 Β· GPL-3.0-only OR Apache-2.0
- ubuntu resolute: cloud-init-base 26.1-0ubuntu3~26.04.1
- ubuntu resolute: cloud-init-base 26.2-0ubuntu1~26.04.1 Β· GPL-3.0-only OR Apache-2.0
- ubuntu stonking: cloud-init-base 26.2-0ubuntu2 Β· GPL-3.0-only OR Apache-2.0
- π girlified by anthropic/claude-haiku-5.5 on : a language model's rewrite of the original, under its terms