Headless Ubuntu Server Installation: A Comprehensive Guide

I’ve installed Ubuntu Server countless times, but doing it without a screen attached is a whole other story. You can’t use the usual installer the same way, so the setup needs a different approach. Let me show you how to do that.

Ubuntu Server’s headless installation can be done using the autoinstall configuration file. The file contains essential setup parameters like partitioning, package selection, profile details, and network configuration, allowing for seamless deployment without needing physical interaction.

I will guide you through the entire process of this headless Ubuntu Server installation. You will also understand how the Ubuntu ISO file is built by extracting and repackaging its files. Finally, you’ll enjoy the automatic installation of your Linux server.

Prerequisites for Ubuntu Headless Installation

Below are some requirements for this project.

Hardware and Software

• Download Ubuntu Server ISO:
  The autoinstall feature only works with Ubuntu 20.04 LTS or newer versions. So, it’s best to choose the latest releases, like Ubuntu Server 26.04 LTS, for compatibility and to access the newest features.
  
• A Linux distribution: The instructions described in this post will work on most Linux systems. In my case, I am using Ubuntu to create the custom setup, but all the tools I’ve used here can be installed on other Linux distros, including Arch-based and RHEL-based distributions.
  
  If you are on a Windows computer, I recommend setting up the Windows Subsystem for Linux (WSL) and installing Ubuntu.
  
  If you are on macOS, the instructions in this tutorial will work perfectly. However, there might be a slight difference in how you install some of these tools.
  
• 7-zip: This is a command line tool that allows users to create, modify, and extract files in various archive formats, including the widely used .zip and .7z formats.
  
  If you are on Ubuntu, use the command below to install it:
  sudo apt install p7zip-full
  If you are on macOS, use Homebrew.
  brew install p7zip
  
• xorriso: This command line tool is used to create, manipulate, and extract ISO image files.
  You can install it on Ubuntu using the command:
  sudo apt install xorriso
If you are on macOS, use the command:
  brew install xorriso

• Prepare the server hardware:
  Once you’ve completed the configurations outlined in this tutorial, you’ll have an ISO file ready to install the Ubuntu server headless.
  
  You can install the Ubuntu server on bare metal or as a virtual machine. Ensure each platform is connected to an active network and has a storage partition prepared for the server installation.

Optional Skills

• Basic command line experience:
  We will get a little technical when preparing the autoinstall configuration file. We will execute several terminal commands and bash scripts.
  
  This tutorial assumes you are well-versed with the Linux terminal commands. You don’t have to be a pro, but some experience would make the setup process much smoother. Going through our Linux command cheatsheet can be helpful.

Understanding the Ubuntu Server Autoinstall feature

The autoinstall feature allows you to install the Ubuntu server without needing a keyboard or display monitor.

Think of it as a “Plug n Play.” In most cases, you will find people calling this method an “unattended,” “hands-off,” or “preseeded” installation.

This feature is exclusively supported in Ubuntu Server 20.04 LTS or later and Ubuntu Desktop 23.04 LTS or later versions. Today, however, we will only talk about the server installation. You can try the same procedure for the desktop version and tell us your experience.

Ubuntu Server Auto-Installation Methods

There are two methods that you can use to install an Ubuntu server headless:

• Directly on the installation media: This method allows embedding the autoinstall configuration directly onto the installation media, allowing for automated setup during the installation process. This is the method that we will use for this tutorial.
  
  This method embeds the autoinstall configuration file directly into the installation media, typically as a YAML file. This YAML file contains instructions dictating how the Ubuntu system should be configured during installation.
  
• Providing #cloud-config user data: This method involves providing configuration directives within cloud-config user data during the boot process, which is then processed by cloud-init. This allows for automated configuration of various aspects of the system during initialization.
  
  This method is widely used in cloud environments such as AWS, Azure, and Google Cloud Platform, but you don’t need to worry about that for this tutorial.

The Structure of an Autoinstall Config

You now understand the two methods available for configuring Ubuntu for auto-installation. For this post, we assume you intend to install Ubuntu Server on a VM or bare-metal without using cloud hosting solutions.

Therefore, we’ll opt for Method 1, which involves creating an autoinstall YAML file containing all our instructions. This method is also known as pre-seeding.

To understand the auto-config file, let’s look at the autoinstall file generated when I installed Ubuntu Server on my Virtual Box VM.

Yes! When you install the Ubuntu Server the usual way (manually), it will generate an autoinstall file in the /var/log/installer directory. This file is named “autoinstall-user-data”.

Now that you understand the autoinstall file let’s prepare our Ubuntu ISO file for headless installation.

Steps to Install Ubuntu “Headless”

Here’s a quick overview of the steps we’ll follow in this tutorial.

• Step 1: Extract the ISO file – Here, we’ll extract the Ubuntu image files so we can manipulate them and add our own configuration files.
• Step 2: Configure autoinstall data – Here, we’ll configure the autoinstall YAML file with all of our custom options.
• Step 3: Edit the GRUB configuration file – In this step, we will edit the bootloader configuration to add a custom “menu-entry” that will appear on the Ubuntu boot screen.
• Step 4: Package the ISO file – Finally, we’ll repackage our files into a new ISO file that we will use to install Ubuntu headless.
• Install Ubuntu server headless – Using the ISO file we prepared, we can install the Ubuntu server headless as a virtual machine or on a bare-metal server.

Let’s go over each one in detail

Step 1. Extract the ISO

In this step, we’ll open up the default ISO so that we can modify its files. I believe you already downloaded the ISO file earlier. Remember, it should be Ubuntu 20.04 LTS or later. In our case, we will be using Ubuntu Server 26.04 LTS.

As I said earlier, we will need to get a bit technical. Launch your terminal and use the ‘cd’ command to navigate to the directory where you have stored the Ubuntu Server ISO file.

To keep our working directory clean, let’s create a folder where we’ll put all the extracted files:
mkdir source-files

Next, we need to extract the ISO file. Use the command below and remember to replace the indented part accordingly:
7z -y x <Ubuntu-ISO-File-Name> -osource-files

Let’s look at this command in detail.

• 7z: This is a command-line utility for compressing and decompressing files.
• -y: This is an option for 7-Zip that stands for “yes.” It instructs 7-Zip to assume “Yes” as the answer to all prompts.
• x: This is the extract command for 7-Zip. It tells 7-Zip to extract files from the specified archive.
• <ubuntu-ISO-File-Name>: This is the placeholder for the name of your Ubuntu ISO file. Replace it with the actual name of the ISO file you want to extract.
• -osource-files: This is an option for 7-Zip that specifies the output directory where the extracted files will be placed. In this case, the extracted files will be placed in a directory named “source-files.” You can change “source-files” to any directory name of your choice.

After a successful extraction, navigate to the directory we created earlier, “source-files,” where everything was stored. You will notice several files and folders extracted when you ran the ls command on this directory.

Here, we are interested in one folder – [BOOT]- containing our boot images. I want us to move this folder up one level as we will need it later to repackage the ISO file.

Use the commands below:
cd source-files
mv '[BOOT]' ../BOOT

Tip: Command lines can be a pain to memorize. I put the essential Linux commands on a printable cheat sheet so you don't have to keep googling them. You can grab the PDF here if you want to save some time.

Step 2. Configure Autoinstall Data

Now, we have come to the sweetest part of this tutorial: preparing the auto-config file. This file will contain all the settings we would have needed to do manually during the Ubuntu installation.

Below is a sample auto-config file I prepared. I took the generated file when I manually installed the Ubuntu server on Virtual Box, then modified it a little.

#cloud-config
autoinstall:
  identity:
    hostname: rpitips
    password: $6$0pBFJFpldJ5c$8wHXpCwT3skkFsJ3Bg9c1lel3TQCr3Qn4U9n6HKucCN73MjKCGjMzv27P9eFw8Ow1uUdPFJy6.kW.GW97Yh.Z/
    username: pat
  kernel:
    package: linux-generic
  keyboard:
    layout: us
    toggle: null
    variant: ''
  locale: en_US.UTF-8
  ssh:
    allow-pw: true
    install-server: true
  updates: security
  version: 1
  shutdown: reboot

Let us quickly go through this file in detail:

• autoinstall: This section contains directives for the automated installation process.
• identity: Specifies identity-related configurations such as hostname, real name, and password.
  • hostname: Sets the hostname of the system to “rpitips.”
  • password: Hashed password for the user account. I’ll show you how to generate a Linux-hashed password in the section below.
  • username: Creates the first user on the system, ‘pat’ in this case.
• kernel: Specifies the kernel package to be installed (in this case, “linux-generic”).
• keyboard: Specifies keyboard layout configurations.
  • layout: Sets the keyboard layout to “us”.
  • locale: Sets the system locale to “en_US.UTF-8”.
• ssh: Specifies SSH-related configurations.
  • allow-pw: Allows password-based SSH authentication.
  • install-server: Installs the SSH server during setup.
• updates: Specifies update preferences (in this case, “security”).
• version: Specifies the version of the autoinstall configuration (version 1).
• shutdown: Specifies the action to be taken after installation completion (in this case, “reboot”).

Tip: You must have realized that my password looks gibberish. Linux stores passwords in the shadow file in an encrypted format. Therefore, that is the encrypted version of my password.

But how did I encrypt the password? Follow the steps below.

• First, make sure ‘mkpasswd’ is installed. It’s usually a part of the “whois” package.
  You can install it if you don’t have it:
  sudo apt install whois
• Once installed, you can use ‘mkpasswd’ to encrypt your password. For example:
  mkpasswd -m sha-512
  This will prompt you to enter the password you want to encrypt.
  

You can utilize my sample file above and modify it according to your preferences. Alternatively, you can visit the official Ubuntu page for a detailed understanding of the structure of the auto-config file.

We will modify our extracted ISO file and add this auto-config file. Use the ‘cd’ command and navigate to the ‘sources-files’ directory:
cd sources-files

Here, we will create one directory, “server,” containing two files, “meta-data” and “user-data.” We will add our configurations inside the “user-data” file. The meta-data file is used for advanced configurations.

mkdir server
touch server/meta-data
touch server/user-data

Once done, please navigate to the server directory we created and open the user-data file using the nano editor shown below.

cd source-files
cd server
nano user-data

This is where we will add our configurations. In my case, I will paste the sample configurations I showed you earlier.

Once done, save the file and exit (CTRL + X).

Step 3. Edit the GRUB Configuration

In this step, we will add a menu item to the bootloader. That way, when we boot the system, it will automatically proceed with our custom headless installation instead of the default one.

While inside the sources-files directory, navigate to the “boot/grub” directory. You should see the GRUB configuration file (grub.cfg) when you run the ‘ls’ command.

cd boot/grub
ls

WARNING: Be careful when running the “cd boot/grub” command. Do NOT write “/boot/grub” or you’ll switch to your running system’s boot directory. That is NOT what you want, as you’ll end up modifying your running system.

The first step is to change the permissions of the “grub.cfg” file, which is typically read-only by default. To accomplish this, we’ll use the ‘chmod’ command:
chmod 644 grub.cfg

Now, we can comfortably edit the grub configuration file. I love using the Nano editor, but you can use Vim or any other editor you choose:
sudo nano grub.cfg

The first parameter we will edit is the “set timeout.” When you start Ubuntu, you will see a boot screen that prompts you to select the image you want to boot. By default, the timeout is set to 30 seconds.

We will reduce it to 5 seconds because we don’t need to select anything. Remember, this is a headless installation:
set timeout=5

Next, we’ll add a new “menuentry” to the grub.cfg file. Essentially, this means we’re adding another option that will appear on the Ubuntu boot screen.

Important: It’s essential to place this new “menuentry” at the top of the existing entries so that it will be automatically selected during boot.

menuentry "Autoinstall Ubuntu Server" {
    set gfxpayload=keep
    linux   /casper/vmlinuz quiet autoinstall ds=nocloud\;s=/cdrom/server/  ---
    initrd  /casper/initrd
}

Let’s have an in-depth look at two parameters in this “menuentry” configuration:

• menuentry “Auto Install Ubuntu Server”: This line defines the menu entry’s title that will appear on the Ubuntu boot screen. In this case, it’s named “Auto Install Ubuntu Server”.
• linux /casper/vmlinuz quiet autoinstall ds=nocloud;s=/cdrom/server/ —: This line specifies the Linux kernel (vmlinuz) and its boot parameters:
  • /casper/vmlinuz: Specifies the path to the Linux kernel image (vmlinuz) within the Ubuntu installation media.
  • quiet: This parameter suppresses most boot messages, resulting in a quieter boot process.
  • autoinstall: Indicates that the installation process should be automated using the autoinstall feature.
  • ds=nocloud\;s=/cdrom/server/: Specifies the location of the cloud-init configuration data. In this case, it’s set to use a local directory (/cdrom/server/) on the installation media.
  • —: Marks the end of kernel parameters.

Save the file and exit.

Step 4. Repackage the ISO File

Now that we have done our configurations, it’s time to repackage all our files into a custom ISO file that we can use to install Ubuntu Server.

To do that, navigate to the “source-files” directory and execute the command below:

xorriso -as mkisofs -r \
  -V 'Ubuntu 26.04 LTS AUTO (EFIBIOS)' \
  -o ../ubuntu-26.04-autoinstall.iso \
  --grub2-mbr ../BOOT/1-Boot-NoEmul.img \
  -partition_offset 16 \
  --mbr-force-bootable \
  -append_partition 2 28732ac11ff8d211ba4b00a0c93ec93b ../BOOT/2-Boot-NoEmul.img \
  -appended_part_as_gpt \
  -iso_mbr_part_type a2a0d0ebe5b9334487c068b6b72699c7 \
  -c '/boot.catalog' \
  -b '/boot/grub/i386-pc/eltorito.img' \
    -no-emul-boot -boot-load-size 4 -boot-info-table --grub2-boot-info \
  -eltorito-alt-boot \
  -e '--interval:appended_partition_2:::' \
  -no-emul-boot \
  .

Now, let’s have a quick look at some of the parameters I have used in this command.

• xorriso: The command-line tool for creating and manipulating ISO filesystem images.
• -as mkisofs: This option instructs xorriso to emulate the behavior of the mkisofs command, which is used for creating ISO images.
• -r: This option stands for “Rock Ridge” and enables Rock Ridge extensions, allowing longer file names and POSIX permissions to be stored in the ISO image.
• -V ‘Ubuntu 26.04 LTS AUTO (EFIBIOS)’: This option specifies the volume label of the ISO image as “Ubuntu 26.04 LTS AUTO (EFIBIOS).”
• -o ../ubuntu-26.04-autoinstall.iso: This option specifies the output file name and path for the generated ISO image.
• –grub2-mbr ../BOOT/1-Boot-NoEmul.img: This option specifies the Master Boot Record (MBR) file to be used for the ISO image. It points to the 1-Boot-NoEmul.img file located in the BOOT directory.
• -partition_offset 16: This option specifies the offset in kilobytes from the start of the ISO image where the partition table should be placed.
• –mbr-force-bootable: This option ensures that the MBR is marked as bootable, indicating that the ISO image can be used to boot a system.
• -append_partition 2 28732ac11ff8d211ba4b00a0c93ec93b ../BOOT/2-Boot-NoEmul.img: This option specifies the second partition of the ISO image, including its size and the path to its boot image (2-Boot-NoEmul.img).
• -appended_part_as_gpt: This option specifies that the appended partition should be treated as a GUID Partition Table (GPT) partition.
• -iso_mbr_part_type a2a0d0ebe5b9334487c068b6b72699c7: This option specifies the type of the ISO MBR partition.
• -c ‘/boot.catalog’: This option specifies the path to the boot catalog file, which contains information about the bootable images in the ISO image.
• -b ‘/boot/grub/i386-pc/eltorito.img’: This option specifies the path to the El Torito boot image used for BIOS booting.
• -no-emul-boot -boot-load-size 4 -boot-info-table –grub2-boot-info: These options configure the boot process for the ISO image, specifying that it should use El Torito booting without emulation, with a boot load size of 4 sectors, and including boot information for GRUB2.
• -eltorito-alt-boot: This option enables alternative El Torito booting, allowing additional boot configurations.
• -e ‘–interval:appended_partition_2:::’: This option specifies the boot image interval for the appended partition.
• -no-emul-boot: This option specifies that the boot image should not be emulated.
• .: This specifies the directory containing the files to be included in the ISO image.

This process should take a little time. Once done, navigate to the directory where you created the “sources-files” folder and run the ls command. You should see the new ISO file we just packaged, “ubuntu-26.04-autoinstall.iso.”

Headless Installation for Ubuntu Server

That’s it! We have completed the complex part. Now you have an ISO file that you can use to install Ubuntu Server on a bare-metal server or as a virtual machine unattended.

If you want to install the Ubuntu server on a PC directly, you have to burn the ISO file to a USB drive. You can use many applications to do that, but I recommend Balena Etcher. Check out this article, which gives you a detailed guide to installing and using Balena Etcher.

If you are installing the Ubuntu server as a virtual machine using an app like VirtualBox or QEMU, you don’t need to create a bootable USB drive. You only need the ISO file.

Tip: Some virtual machine software like VirtualBox tends to implement “unattended” installation features for various operating systems, including Ubuntu. However, we don’t want this feature for our ISO as it might interrupt the booting process. Therefore, ensure you tick the option “skip unattended installation.”

The installation should proceed completely from beginning to end without any input from you. When it’s done, you’ll see your new system’s login screen:

After a successful Ubuntu Server headless installation, you can proceed with configuration as you would with any other system. Begin by ensuring all packages are up-to-date by running the following commands:
sudo apt update
sudo apt upgrade

You may also enhance security by configuring the firewall or transitioning to SSH-key authentication instead of passwords.

For further customization and optimization of your server, consider exploring additional configurations such as setting up user accounts, installing specific software packages, or configuring services according to your requirements.

Not getting the same result?

Even when you follow every step, small differences in OS version, hardware or config can change the outcome. Instead of wasting time guessing, get help from people who have already fixed the same kind of issue.

Ask your question now →

🔒 No risk. Cancel anytime.

• Get help on your exact issue
• Access step-by-step videos for tricky setups
• Browse the website without ads