Article ID: 119080, created on Dec 9, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

Unexpected templates appear in container configuration, after operations like restart/reinstall/migration:

pvc:~# vzpkg list 111
centos-6-x86_64                    2012-10-24 21:33:15
centos-6-x86_64      mysql         2013-12-06 14:09:36
centos-6-x86_64      php           2013-12-06 14:09:36

pvc:~# vzctl reinstall 111

pvc:~# vzpkg list 111
centos-6-x86_64                    2012-10-24 21:33:15
centos-6-x86_64      mysql         2013-12-06 14:38:21
centos-6-x86_64      php           2013-12-06 14:38:21
centos-6-x86_64      yum           2013-12-06 14:38:21 

Cause

Parallels Virtuozzo Containers tries to detect packages installed inside containers and replaces the set of packages with the corresponding application templates.

Resolution

Disable template autodetection in /etc/vztt/vztt.conf:

~# grep APP_TEMPLATE_AUTODETECTION /etc/vztt/vztt.conf
APP_TEMPLATE_AUTODETECTION=no

Additional details

In the above example, yum template is added to the container configuration file, as it includes just a single "yum" package in its list of packages, and centos-6 containers come with yum installed as a part of the OS template.

[root@pvc ~]# grep yum /vz/template/centos/6/x86_64/config/os/default/packages
yum

[root@pvc ~]# cat /vz/template/centos/6/x86_64/config/app/yum/default/packages
yum

Related articles

Container reinstallation fails because of application templates conflict

Search Words

packages template

Error: /usr/share/vzyum/bin/yum failed, exitcode=1

template autodetection

vzpkg sync_vzpackages

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF