proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-08-10 13:28:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pct: improve template/images section

Browse Source 
Bring the usage in order, cannot create a CT from a template before
we downloaded it ;)

Also (re)-mention the web interface as a TIP.
cron job was replaced by systemd timer, adapt that too.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2020-02-17 11:47:32 +01:00
parent b0df9949dc
commit 2a368b1e0d
1 changed files with 14 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
pct.adoc
View File

@ -92,11 +92,6 @@ Container Images
Container images, sometimes also referred to as ``templates'' or
``appliances'', are `tar` archives which contain everything to run a container.
`pct` uses them to create a new container, for example:
----
# pct create 999 local:vztmpl/debian-10.0-standard_10.0-1_amd64.tar.gz
----
{pve} itself provides a variety of basic templates for the most common Linux
distributions. They can be downloaded using the GUI or the `pveam` (short for
@ -104,8 +99,8 @@ distributions. They can be downloaded using the GUI or the `pveam` (short for
Additionally, https://www.turnkeylinux.org/[TurnKey Linux] container templates
are also available to download.
The list of available templates is updated daily via cron. To trigger it
manually:
The list of available templates is updated daily through the 'pve-daily-update'
timer. You can also trigger an update manually by executing:
----
# pveam update
@ -144,9 +139,9 @@ system ubuntu-19.10-standard_19.10-1_amd64.tar.gz
----
Before you can use such a template, you need to download them into one of your
storages. You can simply use storage `local` for that purpose. For clustered
installations, it is preferred to use a shared storage so that all nodes can
access those images.
storages. If you're unsure to which one, you can simply use the `local` named
storage for that purpose. For clustered installations, it is preferred to use a
shared storage so that all nodes can access those images.
----
# pveam download local debian-10.0-standard_10.0-1_amd64.tar.gz
@ -160,6 +155,15 @@ downloaded images on storage `local` with:
local:vztmpl/debian-10.0-standard_10.0-1_amd64.tar.gz 219.95MB
----
TIP: You can also use the {pve} web interface GUI to download, list and delete
container templates.
`pct` uses them to create a new container, for example:
----
# pct create 999 local:vztmpl/debian-10.0-standard_10.0-1_amd64.tar.gz
----
The above command shows you the full {pve} volume identifiers. They include the
storage name, and most other {pve} commands can use them. For example you can
delete that image later with: