linux ubuntu virtualization vmware-vsphere virtualbox – Set Password on Ubuntu Cloud Image

linuxUbuntuvirtualboxvirtualizationvmware-vsphere

I'm trying to start on .ova with VirtualBox and want to import the same image later in vSphere.

Ubuntu cloud images don't have a standard password anymore.

I'd like to edit the .ova to configure a password. (and later SSH keys)

The downloaded .ova does have a password property.

I found a tool called cot (Common OVF tool) to edit the properties.

I tried:

cot edit-properties ubuntu-18.04-server-cloudimg-amd64-custom.ova -p password=ubuntu

Also also tried:

cot edit-properties ubuntu-18.04-server-cloudimg-amd64-custom.ova -p user-data="password: ubuntu"

Both attempts without success. (unable to login)

Is there a step to apply this configuration into the images, or do these properties get passed to the image when it starts?

Any ideas?

Updated: (answers to background questions)

  1. As a first step I want root access, so I can test the network setup of adapter, bridge, routes, DNS.
  2. A new user with ssh key and sudo is 2nd goal.
  3. Ubuntu 17.10 (soon 18.04)
  4. VirtualBox 5.2.14
  5. vSphere 5.5

Best Answer

Questions

It would be useful if you could add background information to the question, like:

  1. Why do you need to set a root password. Maybe there is an alternative way. What are you trying to accomplish?
  2. According to (1), the recommended way might be one among several options: root user with password, a new user with ssh key and sudo, others.)
  3. What's your host operating system?
  4. VirtualBox version?
  5. VMWare vsphere version?

General plan

  1. Set the correct settings for Virtualbox
  2. Create the user-data and meta-data files
  3. Generate the ISO image for cloud-init
  4. Boot the VM with the attached ISO image as a removable device

Virtualbox

  1. You can import the OVA as an appliance, use an IMG or VMDK disk. You can do this in the GUI or the command line.
  2. You should enable the serial port in the hardware settings for the VM. Optionally, point it to a raw file in your home, so you can see the log in case of problems.
  3. You need the iso/img generated below for cloud-init and mount it in the dvd or cd device for the VM you imported. If the VM doesn't include a dvd/cd device, you have to add one. Add it as IDE and master, then load the ISO generated below.

Cloud-Init

If you are using the Ubuntu Cloud Images, you should use Cloud-Init for setting the initial configuration, it allows you to set up:

  • Default locale
  • Hostname
  • Generating and setting up SSH private keys

... among other features.

Cloud-init's behavior can be configured via the user-data flag for inline commands or calling a YAML type config file with the settings to apply.

This is might be done via the --user-data or --user-data-file argument when you are running inline, or you can do it with the ISO. I'm going to show the steps for the ISO mount mode.

I will not setup a password for root or the user, I'm creating instead a new user with SSH access via ssh public keys and allowing the user sudo permissions instead.

Here is a sample user-data cloud-config file, create it with your text editor, and respect the name or the seed file won't be a valid seed and won't work.

#cloud-config
users:
  - default
  - name: eddypronk
    ssh-authorized-keys:
      - <your user public key here>
    sudo: ALL=(ALL) NOPASSWD:ALL
    groups: sudo
    shell: /bin/bash

You can also have a meta-data for the hostname and other definitions:

instance-id: set-an-unique-instance-name-id
local-hostname: set-the-hostname

After creating the files generate an iso file to load as a cdrom or dvd from the virtual manager:

genisoimage -output nocloud.iso -volid cidata -joliet -rock user-data meta-data

You need genisoimage for this or the cloud-utils tool cloud-localds for this other option:

cloud-localds my-seed.img my-user-data my-meta-data

Remember that if you leave the seed / nocloud iso mounted, it will ovewrite the settings in the VM with those in the data files. And if you change anything in user-data or meta-data you need to rebuild the iso or img.

Boot

You can now boot the VM. By default, you can not ssh to the machine using the username and password or connect through the VNC console (the "graphical" VM window in Virtualbox). You have to use public / private key authentication method with ssh. This means enabling a user with a public ssh key in the user-data YAML file. Also, sudo privileges elevation for the ubuntu account is passwordless, but the account is locked by default.

Related Topic