Proxmox VE – How to build an Ubuntu 22.04 Template (Updated Method)

33 thoughts on “Proxmox VE – How to build an Ubuntu 22.04 Template (Updated Method)”

• Very good, excelent tutorial, recomended

• Linux n00bie. I've tried this 3 times and I always end up with vms that get stuck on "starting serial terminal on interface <interface>". This doesn't happen all the time, the first time it was because of my network settings, but now it's just intermittent and I can't figure out why. Any pointers on where to look?

• Seems that downside with this approach that installing custom things won't be part of the template? Such as the Qemu agent, and any other default packages you want setup in the template. Any way to solve that with this method, or follow the old video?

• Perfect explanation.

  Can I install qemu agent on template itself ?
  Can I regenerate cloud image on new template based machine to have different user name

  Can templates also be backed up to PBS .

• Set up with network storage by adjusting the command like 'qm importdisk 900 ubuntu-22.04.qcow2 nfsstorage' – the disk showed up as a '.raw' format but still worked flawlessly.

• Great video Jay! Thanks 🙂 i am trying to create Ubuntu 22.04 Template but i don't understand when you add the ssh key to it . i mean where you get the ssh key ? Thanks

• Is there another step if I don't have an ssh public key? If i try to log on from powershell I get permission denied (public key). Any help would be greatly appreciated. 🙂

• I would like to add a little to one of the posts here in the comments, a few necessary first steps with the system image:

  1. virt-customize -a yaimage.img –install qemu-guest-agent
  2. virt-customize -a yaimage.img –run-command "sudo echo > /etc/machine-id; sudo ln -sf /etc/machine-id /var/lib/dbus/machine-id"
  …and what I do also:
  3. virt-customize -a yaimage.img –root-password password:yourpass – set root password
  4. virt-customize -a yaimage.img –timezone "Europe/Kiev" – set ya time zone
  5. virt-customize -a yaimage.img –install <package_name> – install some packages, for example qemu-guest-agent
  6. virt-edit yaimage.img /etc/cloud/cloud.cfg – system setup, for example enable root
  7. virt-edit yaimage.img /etc/ssh/sshd_config – ssh setup, for example enable password authentication and etc…

  Wsup!

• Your are great and explain everything in detail. I like your work!

• Your videos are always so clear. Step-by-step. Very helpful. Very much appreciate the videos you produce on YouTube!

• I wish I could put more than one like on this video 😉

• Is this for all Linux distros or just for Ubuntu?

• Nice video! Covered the basics. Now going to more advanced question: How to create customized template? Lets say I want to have a template with the qemu-guest-agent already installed instead of me going to the server and installing it manually, then how to proceed?

• This is literally the best guidance and so well delivered. Definitely like and subscribe!

• Hi,
  thanks for this tutorial, I have one issue please if you could help,
  I have followed the same instruction but when I typed ip a to see the @ip, I dont see it, (I have choosed DHCP in cloud-init as you did), do you know please what could be the problem ?

• 11:30 or just read the manual
  12:22 no need, you can 'qm set 900 –scsi0 local-lvm:0,import-from=/root/ubuntu-22.04-minimal-cloudimg-amd64.img' and resize via GUI later.

• thanks Jay !

• Can you install qemu directly in the template ?
  Thanks for the video

• Hello Jay! Great video. When I clone the template and boot the VM I get the Grub rescue prompt everytime

• I found this useful, so I'm leaving a vapid comment to appease our algorithmic overlords.

• qm importdisk $id /mnt/pve/pve-iso/template/iso/jammy-server-cloudimg-amd64.img pve-guests –format qcow2

• For those that want to use machine q35 use the following command to change the cloudinit from ide2 to scsi
  qm set {VMID} –scsi1 local-lvm:cloudinit

• If you're on MacOS, for qemu-quest-agent to work with the SSH key, I had to add a Host entry to my ~/.ssh/config file:
  Host *
  AddKeysToAgent yes
  UseKeychain yes
  IdentityFile ~/.ssh/generated_key_name

• Great video! Thnx a lot!

• Hello Jay,
  first i want to thank You for great tutorial.
  But always when i setup template and using cloud-init from Proxmox (without configuring SSH public key option) i have problem to login to VM (created from template) via ssh – Permission denied (publickey) . Can you give me some advise how to do it?
  Many thanks.

• great video, accurate instructions and work like a charm, thanks Jay

• Hi Jay, I just noticed that the minimal image that you are working with in your tutorial is the same as the one used for the Container image. Cheers

• I appreciate your youtube videos, and the way you explain.
  
  Looking at the video I found that you have more Bridges for different purposes.

  On the internet it is not explained clearly how to route traffic between these bridges to have the machines encapsulated under one bridge. There are some examples with NAT.
  
  Also is possible to do with VLANS instead of bridges but also is not clear.

  If you have time, it will be nice to cover this theme, because there is very little info on the net.

  Thank you very much.

• 13:00 qemu can use qcow2 or raw filesystem images. With Raw there's now way for qemu to determine it's actually format because there's not file header say "This is disk image" it just has to guess. (A raw file image could be completely blank). If you pass raw direclty to qemu it'll give a warning say you should use the format=raw option to avoid issues.
  With the file extension qemu assumes it's a qcow2 image. It could guess based on filestrcture if it's qcow2 file anyway, it's very unlinkly it could be a raw image with data that looks like qcow2 anwyay.

• Thank you very much, again. Very useful.

• Is it possible to create a template with the qemu agent already installed so it's ready to go? #linuxnoobalert

• the reason why you have to add a Cloudinit Drive CD-ROM to vm is because the custom cloud-init config will be "burned" to this CD-ROM, so when the attached vm is being started, the cloud-init inside of it can detect the corresponding filesystem (with fs label `cidata` and fs type `iso9660`) the CD-ROM provides, you can observe the `mount and umount of /dev/sr0 (which is cloud-init drive CD-ROM)` behaviour within /var/log/cloud-init.log, hopefully this helps!

• i have kvm running raw and cloudinit installs the qemu agent as part of update to cloudimage. – can proxmox not do that

Comments are closed.