In systems that use systemd and have a current (17.0+) version of cloud-init, upstream documentation describes the process for disabling cloud-init with either of the following:
cloud-init=disabled to the kernel command line.
For older versions of cloud-init (0.7.X) the following information might be useful.
You can disable cloud-init's modification of /etc/fstab in one of 2 ways.
a.) by providing cloud-config that overrides the default 'mounts' entries and disables them.
- [ephemeral0, null]
- [swap, null]
b.) by disabling the
mounts module from running. This is done by removing it from the 'cloud_config_modules' list that you'll see in
With regard to hostname, you can also control that also. If you just want to stop cloud-init from modifying /etc/hostname, then:
Also interesting to you might be
Both of these are documented in doc/examples/cloud-config.txt (and installed in
I'm interested in knowing how cloud-init is breaking /etc/fstab, though. Please file a bug using
ubuntu-bug cloud-init from inside your instance, and describe what it is doing that you think is wrong.