proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-28 07:37:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pct: move "guest OS config" below CT settings

Browse Source 
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2020-02-14 17:26:27 +01:00
parent da9679b6bd
commit 0892a2c279
1 changed files with 66 additions and 66 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

132
pct.adoc
View File

@ -106,72 +106,6 @@ To trace AppArmor activity, use:
# dmesg | grep apparmor
----
Guest Operating System Configuration
------------------------------------
{pve} tries to detect the Linux distribution in the container, and modifies
some files. Here is a short list of things done at container startup:
set /etc/hostname:: to set the container name
modify /etc/hosts:: to allow lookup of the local hostname
network setup:: pass the complete network setup to the container
configure DNS:: pass information about DNS servers
adapt the init system:: for example, fix the number of spawned getty processes
set the root password:: when creating a new container
rewrite ssh_host_keys:: so that each container has unique keys
randomize crontab:: so that cron does not start at the same time on all containers
Changes made by {PVE} are enclosed by comment markers:
----
# --- BEGIN PVE ---
<data>
# --- END PVE ---
----
Those markers will be inserted at a reasonable location in the file. If such a
section already exists, it will be updated in place and will not be moved.
Modification of a file can be prevented by adding a `.pve-ignore.` file for it.
For instance, if the file `/etc/.pve-ignore.hosts` exists then the `/etc/hosts`
file will not be touched. This can be a simple empty file created via:
----
# touch /etc/.pve-ignore.hosts
----
Most modifications are OS dependent, so they differ between different
distributions and versions. You can completely disable modifications by
manually setting the `ostype` to `unmanaged`.
OS type detection is done by testing for certain files inside the
container:
Ubuntu:: inspect /etc/lsb-release (`DISTRIB_ID=Ubuntu`)
Debian:: test /etc/debian_version
Fedora:: test /etc/fedora-release
RedHat or CentOS:: test /etc/redhat-release
ArchLinux:: test /etc/arch-release
Alpine:: test /etc/alpine-release
Gentoo:: test /etc/gentoo-release
NOTE: Container start fails if the configured `ostype` differs from the auto
detected type.
[[pct_container_images]]
Container Images
----------------
@ -642,6 +576,72 @@ It will be called during various phases of the guests lifetime. For an example
and documentation see the example script under
`/usr/share/pve-docs/examples/guest-example-hookscript.pl`.
Guest Operating System Configuration
------------------------------------
{pve} tries to detect the Linux distribution in the container, and modifies
some files. Here is a short list of things done at container startup:
set /etc/hostname:: to set the container name
modify /etc/hosts:: to allow lookup of the local hostname
network setup:: pass the complete network setup to the container
configure DNS:: pass information about DNS servers
adapt the init system:: for example, fix the number of spawned getty processes
set the root password:: when creating a new container
rewrite ssh_host_keys:: so that each container has unique keys
randomize crontab:: so that cron does not start at the same time on all containers
Changes made by {PVE} are enclosed by comment markers:
----
# --- BEGIN PVE ---
<data>
# --- END PVE ---
----
Those markers will be inserted at a reasonable location in the file. If such a
section already exists, it will be updated in place and will not be moved.
Modification of a file can be prevented by adding a `.pve-ignore.` file for it.
For instance, if the file `/etc/.pve-ignore.hosts` exists then the `/etc/hosts`
file will not be touched. This can be a simple empty file created via:
----
# touch /etc/.pve-ignore.hosts
----
Most modifications are OS dependent, so they differ between different
distributions and versions. You can completely disable modifications by
manually setting the `ostype` to `unmanaged`.
OS type detection is done by testing for certain files inside the
container:
Ubuntu:: inspect /etc/lsb-release (`DISTRIB_ID=Ubuntu`)
Debian:: test /etc/debian_version
Fedora:: test /etc/fedora-release
RedHat or CentOS:: test /etc/redhat-release
ArchLinux:: test /etc/arch-release
Alpine:: test /etc/alpine-release
Gentoo:: test /etc/gentoo-release
NOTE: Container start fails if the configured `ostype` differs from the auto
detected type.
Backup and Restore
------------------