TINY-CLOUD.CONF(5)
π¦ tiny-cloud.conf(5) β the config file, bestie edition π¦
okay so this is the tiny-cloud.conf manual page, section 5 of the File Formats Manual, and honestly? it's giving "tiny file, huge main character energy." let's get into it π
β¨ NAME β¨
tiny-cloud.conf β the configuration file for tiny-cloud π
π DESCRIPTION π
tiny-cloud.conf is literally the config file for tiny-cloud(8). here's the tea: the file gets sourced by the tiny-cloud shell code during startup, so it's not some fancy custom format β it's just shell-style variable assignments. periodt. π
the default system configuration file is /etc/tiny-cloud.conf. remember that path, bestie, you'll need it πΈ
π FORMAT π
the file is made of shell variable assignments that look like this:
NAME=value
blank lines and shell comments? ignored. not invited to the party. bye π
π VARIABLES π
this is the part you actually came for, so buckle up π«Ά
CLOUD=<provider>β picks your cloud provider. default isauto, which turns on provider autodetection (she'll figure it out herself, she's smart like that β¨). supported values rn includeaws,azure,digitalocean,gcp,hetzner,incus,nocloud,oci,openstack, andscalewayπCLOUD_USER=<user>β the default user account for instance SSH keys and default-user setup. default isalpine. iconic name choice ngl ποΈTINY_CLOUD_INIT_SYSTEM=<init_system>β which init system gets used for service management. supported values areauto,openrc, andsystemd. default isauto, which sniffs out the running init system for you πβ¨IMDS_API_VERSION=<version>β the provider's API version to use. providers that have versioned APIs come with built-in default values already, so you don't gotta worry πIMDS_ENDPOINT=<address[:port]>β the provider endpoint IP address or hostname to use. defaults to169.254.169.254for many providers π«‘IMDS_ENDPOINTS=<endpoint> ...β a whitespace-separated list of provider endpoints. defaults toIMDS_ENDPOINT. endpoints are tried in order, and the most recently working endpoint gets tried first on later queries (she remembers what worked, queen behavior π). IPv6 endpoints must use brackets, for example[fd00:ec2::254]or[fd00:ec2::254]:80β οΈIMDS_ENDPOINT_WAIT_ATTEMPTS=<number>β how many times to check for routes to any IMDS endpoint before just trying metadata requests anyway. default is10πIMDS_TOKEN_TTL=<seconds>β metadata token lifetime in seconds for AWS metadata access. only the AWS provider uses this one. default is5β³AZURE_WIRESERVER=<address>β the Azure WireServer address used to report provisioning readiness. only the Azure provider uses this. default is168.63.129.16βοΈAZURE_READY_ATTEMPTS=<number>β how many attempts to make when reporting provisioning readiness to Azure. default is5π―AZURE_READY_RETRY_DELAY=<seconds>β the delay between Azure provisioning-readiness attempts. default is5β±οΈTINY_CLOUD_DHCP_TIMEOUT=<seconds>β max number of seconds to wait for temporary bootstrap DHCP. default is10π‘TINY_CLOUD_DHCP_CLIENT=<auto|dhcpcd|udhcpc>β which DHCP client to use for temporary bootstrap networking and generated network configuration. defaultautousesdhcpcdwhen it's available and otherwise falls back toudhcpc. heads up: selectingdhcpcdrequires it to be installed, and selectingudhcpcdisables use ofdhcpcdentirely π«ΆPRESERVE_NETWORK_INTERFACES=<0|1>β when set to1and/etc/network/interfacesalready exists, keep that file instead of replacing it with datasource-provided network configuration. if the file doesn't exist, normal datasource and fallback processing carries on like nothing happened π« default is0. this currently affects NoCloud, aka the provider that supports datasource-provided network configuration πTINY_CLOUD_VAR=<path>β the state directorytiny-clouduses. default is/var/lib/cloudπTINY_CLOUD_LOGS=<path>β the log directorytiny-clouduses. default is/var/logπͺ΅TINY_CLOUD_LV_ALLOCATE=<percentage>β how much space to allocate when expanding the"/"LVM logical volume, as a percentage. default is85percent of the volume group's space πΎSKIP_INIT_ACTIONS=<action> ...β whitespace-separated list of init actions to skip during phase execution. common action names includeexpand_root,set_hostname,set_ssh_keys,save_userdata, andrun_userdataπ ββοΈNONFATAL_INIT_ACTIONS=<action> ...β whitespace-separated list of init actions whose failure gets logged without stopping the phase. default isset_ephemeral_network save_userdataπ©Ή
π EXAMPLES π
force the AWS provider:
CLOUD=aws
use a different default login account:
CLOUD_USER=ec2-user
force systemd service management:
TINY_CLOUD_INIT_SYSTEM=systemd
preserve image-provided network interfaces:
PRESERVE_NETWORK_INTERFACES=1
skip hostname and SSH key setup:
SKIP_INIT_ACTIONS="set_hostname set_ssh_keys"
π SEE ALSO π
tiny-cloud(8), imds(1) β go read those too, they're literally so good π§
and that's the whole page, bestie!! this one's from the File Formats Manual, dated 2026-08-24 β tape it to your mirror and go configure something iconic πβ¨
π¦ where this page comes from
- alpine 3.24: tiny-cloud-doc 3.4.1-r2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms