Changes for page proxmox

Last modified by Kevin Wiki on 2026/05/18 15:44

From 2.4 to 3.1 From 11.3 to 11.4

From version

3.1

edited by Kevin Wiki
on 2025/07/05 20:18

Change comment: There is no comment for this version

To version

11.3

edited by Kevin Wiki
on 2026/05/18 15:40

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- image.jpg

Details

Page properties

Content

@@ -17,14 +17,20 @@
  To view the available LXC templates:
++{{code language="bash"}}
  pveam list
++{{/code}}
++
  === Download Templates ===
  Use the pveam download command to import templates to the local storage:
++{{code language="bash"}}
  pveam download local ubuntu-22.04-standard_22.04-1_amd64.tar.gz
  pveam download local ubuntu-24.04-standard_24.04-1_amd64.tar.zst
  pveam download local debian-12-standard_11.7-1_amd64.tar.zst
++{{/code}}
++
  Once downloaded, these templates can be used to create new LXC containers from the Proxmox web interface or via CLI.
  == VM Template from Ubuntu Cloud Image ==
@@ -33,22 +33,32 @@
  === Download Ubuntu Cloud Image ===
--Download the official Ubuntu 24.04 cloud image:
++Download the official Ubuntu 24.04 cloud [[image:]]
++{{code language="bash"}}
  wget http://cloud-images.ubuntu.com/releases/24.04/release/ubuntu-24.04-server-cloudimg-amd64.img
++{{/code}}
++
  === Create the Virtual Machine ===
  Create a new VM with ID 910 (you can pick any unused ID):
++{{code language="bash"}}
  qm create 910 -name template-ubuntu-jammy -memory 2048 -net0 virtio,bridge=vmbr0 -cores 2 -sockets 1
++{{/code}}
++
  === Import and Attach the Disk ===
  Choose the correct storage (replace nvme if you use a different storage name):
++{{code language="bash"}}
  qm importdisk 910 ubuntu-24.04-server-cloudimg-amd64.img nvme
  qm set 910 -scsihw virtio-scsi-pci -virtio0 nvme:vm-910-disk-0
++{{/code}}
++
  === Configure the VM ===
++{{code language="bash"}}
  qm set 910 -serial0 socket
  qm set 910 -boot c -bootdisk virtio0
  qm set 910 -agent 1
@@ -57,13 +57,206 @@
  qm set 910 -vga qxl
  qm set 910 -ide2 nvme:cloudinit
  qm resize 910 virtio0 +8G
++{{/code}}
++
++
  If your disk is using SCSI instead of virtio, resize like this:
++
++{{code language="bash"}}
  qm resize 910 scsi0 +8G
++{{/code}}
++
  === Convert the VM into a Template ===
++{{code language="bash"}}
  qm template 910
++{{/code}}
++
  Now you can use this template to clone new VMs instantly.
++== Bash Script to Automate Setup ==
++
++Install the above using bash script below
++
++=== setup_proxmox_templates.sh ===
++
++{{code language="bash"}}
++#!/bin/bash
++
++# Exit on errors
++set -e
++
++echo "Downloading LXC templates..."
++pveam download nvme ubuntu-22.04-standard_22.04-1_amd64.tar.zst
++pveam download nvme ubuntu-24.04-standard_24.04-2_amd64.tar.zst
++pveam download nvme alpine-3.21-default_20241217_amd64.tar.xz
++pveam download nvme debian-12-standard_12.7-1_amd64.tar.zst
++
++echo "Downloading Ubuntu cloud image..."
++wget -N http://cloud-images.ubuntu.com/releases/24.04/release/ubuntu-24.04-server-cloudimg-amd64.img
++
++echo "Creating VM Template..."
++qm create 910 -name template-ubuntu-jammy -memory 2048 -net0 virtio,bridge=vmbr0 -cores 2 -sockets 1 && 1
++
++# qm importdisk 910 ubuntu-24.04-server-cloudimg-amd64.img nvme
++# qm set 910 -scsihw virtio-scsi-pci -scsi0-virtio0 nvme:910/vm-910-disk-0
++qm set 910 -scsihw virtio-scsi-pci -scsi0 nvme:0,import-from=/mnt/nvmestorage/template/iso/ubuntu-24.04-server-cloudimg-amd64.img
++
++qm set 910 -serial0 socket
++qm set 910 -boot c -bootdisk virtio0
++qm set 910 -agent 1
++qm set 910 -hotplug disk,network,usb
++qm set 910 -vcpus 1
++qm set 910 -vga qxl
++qm set 910 -ide2 nvme:cloudinit
++# qm resize 910 scsi0 +8G
++
++read -p "Confirm converting to template by pressing Enter"
++qm template 910
++
++echo "Templates setup complete."
++{{/code}}
++
++
++= VM runtime setup =
++
++After creating the VM and before making it into a template there are some programs and settings we want to ensure exists always.
++
++(% id="cke_bm_721114S" style="display:none" %)** **(%%)**clear bash history** to not leave any configuration in history, clear and disable history file before proceeding:
++
++{{code language="bash"}}
++unset HISTFILE
++export HISTSIZE=0
++export HISTFILESIZE=0
++
++sudo rm /.bash_history
++rm ~/.bash_history
++{{/code}}
++
++**qemu-guest-agent** is for allowing proxmox to query information from the VM such as IP address, shutdown commands, etc
++
++{{code language="bash"}}
++sudo apt update
++sudo apt upgrade -y
++sudo apt install qemu-guest-agent -y
++
++sudo systemctl enable qemu-guest-agent.service
++sudo systemctl start qemu-guest-agent.service
++{{/code}}
++
++**reset machine-id** to not have overlapping ids from same template
++
++{{code language="bash"}}
++cat /dev/null > /etc/machine-id
++cat /dev/null > /var/lib/dbus/machine-id
++{{/code}}
++
++**cloud-init** is a great hook for installing or configuring programs or receiving variables from cloudinit CDROM drive. Making it easier to change IP, hostname, DNS, username/password, etc between VMs.
++
++If you used a cloud-init base image it will have run the default cloudinit which installs and confi
++
++{{code language="bash"}}
++cloud-init clean
++{{/code}}
++
++This is a debian example of what we are looking for:
++
++{{code language="yaml"}}
++# The top level settings are used as module
++# and system configuration.
++# A set of users which may be applied and/or used by various modules
++# when a 'default' entry is found it will reference the 'default_user'
++# from the distro configuration specified below
++
++# If this is set, 'root' will not be able to ssh in and they
++# will get a message to login instead as the default $user
++disable_root: true
++
++# This will cause the set+update hostname module to not operate (if true)
++preserve_hostname: false
++
++apt:
++   # This prevents cloud-init from rewriting apt's sources.list file,
++   # which has been a source of surprise.
++   preserve_sources_list: true
++
++# manually managed resolv
++manage_resolv_conf: false
++
++package_update: true
++packages:
++  - qemu-guest-agent
++
++# The modules that run in the 'init' stage
++cloud_init_modules:
++ - seed_random
++ - bootcmd
++ - write-files
++ - growpart
++ - resizefs
++ - disk_setup
++ - mounts
++ - set_hostname
++ - update_hostname
++ - update_etc_hosts
++ - ca-certs
++ - rsyslog
++ - users-groups
++ - ssh
++
++# The modules that run in the 'config' stage
++cloud_config_modules:
++ - keyboard
++ - locale
++ - set-passwords
++ - grub-dpkg
++ - apt-pipelining
++ - apt-configure
++ - ntp
++ - timezone
++ - disable-ec2-metadata
++ - runcmd
++
++# The modules that run in the 'final' stage
++cloud_final_modules:
++ - package-update-upgrade-install
++ - write-files-deferred
++ - scripts-vendor
++ - scripts-per-once
++ - scripts-per-boot
++ - scripts-per-instance
++ - scripts-user
++ - ssh-authkey-fingerprints
++# - keys-to-console
++ - install-hotplug
++# - phone-home
++ - final-message
++ - power-state-change
++
++runcmd:
++  - systemctl enable qemu-guest-agent.service
++
++# System and/or distro specific settings
++# (not accessible to handlers/transforms)
++system_info:
++   # This will affect which distro class gets used
++   distro: debian
++   # Other config here will be given to the distro class and/or path classes
++   paths:
++      cloud_dir: /var/lib/cloud/
++      templates_dir: /etc/cloud/templates/
++   package_mirrors:
++     - arches: [default]
++       failsafe:
++         primary: https://deb.debian.org/debian
++         security: https://deb.debian.org/debian-security
++   ssh_svcname: ssh
++{{/code}}
++
++
++
++
++
  )))

image.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.kevin

Size

...	...	@@ -1,1 +1,0 @@
1		-40.8 KB

Content

Changes for page proxmox

Summary

Details

Navigation

Recently Modified