1. set cloud-init or perl scripts as the customization engine
1) if you want to set cloud-init as the customization engine by:
Set “disable_vmware_customization: false" in "/etc/cloud.cfg"
2) if you want to set perl script as customization engine, you should disable or remove
cloud-init
Disable cloud-init service by running this command:
sudo touch /etc/cloud/cloud-init.disabled
Remove cloud-init package and purge the config files by running these commands:
sudo apt-get purge cloud-init
2. Open the /usr/lib/tmpfiles.d/tmp.conf file.
Go to the line 11 and add the prefix #.
or example:
#D /tmp 1777 root root -
3. If you have open-vm-tools installed, open the /lib/systemd/system/open-vm-tools.service file.
Add “After=dbus.service” under [Unit].
Currently we have workaround for it.
Workaround:
1. set cloud-init or perl scripts as the customization engine vmware_ customization: false" in "/etc/cloud.cfg"
1) if you want to set cloud-init as the customization engine by:
Set “disable_
2) if you want to set perl script as customization engine, you should disable or remove
cloud-init
Disable cloud-init service by running this command: cloud-init. disabled
sudo touch /etc/cloud/
Remove cloud-init package and purge the config files by running these commands:
sudo apt-get purge cloud-init
2. Open the /usr/lib/ tmpfiles. d/tmp.conf file.
Go to the line 11 and add the prefix #.
or example:
#D /tmp 1777 root root -
3. If you have open-vm-tools installed, open the /lib/systemd/ system/ open-vm- tools.service file. dbus.service” under [Unit].
Add “After=