You can specify several objects to install into the container by separating them by spaces. When executed, vzpkg install automatically handles the interdependencies among the packages to be installed into a container and ensures that all dependencies are satisfied.
If the package dependencies cannot be resolved, the installation process fails and the corresponding message is displayed. Makes the vzpkg install command look for the packages included in the EZ template in the local vzpkg cache only.
If there is a package not available locally, the command will fail. Simulates the same operations as vzpkg install completes without specifying this option downloads the software packages to the server, handles the package interdependencies, etc. By default, the specified object is treated by vzpkg install as an application EZ template.
However, you can use the -p or -g option to explicitly specify the type of the object. A container has to be running in order to apply an application EZ template to or install a package inside this container. The vzpkg update command is used to update the following components of a container:.
Makes the vzpkg update command look for the package updates in the local vzpkg cache only. Updates the packages installed in the container by using the vzpkg install command. Updates the YUM software group in the container. Simulates the same operations as vzpkg update completes without specifying this option downloads the updated packages to the server, handles their interdependencies, etc. Without any options specified, vzpkg update updates all EZ templates including the OS EZ template in the specified container.
You can also use the -p or -g option to update YUM software groups or individual software packages in the container. This command is used to remove an application EZ template, YUM software group, or a software package from a container. You may specify a number of objects for removing. Removes the specified YUM software group from the container. Simulates the same operations as vzpkg remove completes without specifying this option handles interdependencies of the packages to be removed from the server, etc.
By default, the specified object is treated by vzpkg remove as an application EZ template. This command is used to create tarballs caches for OS EZ templates. You should execute this command before you start using a newly installed OS EZ template for creating containers. Makes the vzpkg create cache command check for the packages included in the EZ OS template in the local vzpkg cache only and use them for the cache creation.
In this case vzpkg create cache will also check the local vzpkg cache only. When a container is being created, prlctl just unpacks the tar archive. By default, vzpkg create cache checks the tar archive existence for all OS EZ templates installed on the server and creates some, if necessary.
If the cache of the OS template specified already exists on the server, the command will fail and you will be presented with the corresponding error message. Makes the vzpkg update cache command check for the packages updates in the local vzpkg cache only and use them for the cache creation. In this case vzpkg update cache will also check the local vzpkg cache only.
Upon the vzpkg update cache execution, the old tarball is renamed by receiving the -old suffix e. You should use the -rm command to delete these caches from the server.
If the OS EZ template cache has not been created yet, this will be done before application templates are added. Specifies the path to the configuration file with the information on what OS and application templates to use. Specifies the OS EZ template to use in cache creation.
This option redefines the OS EZ template specified in the configuration file. Specifies one or more application EZ templates comma-separated to be added to the resulting cache.
This option redefines the application EZ templates specified in the configuration file. This command updates an existing OS EZ template cache with preinstalled application templates if the --update-cache option is provided. To list templates available for installation in the official remote repositories, run the following command:. Configure additional template parameters if needed.
Some of the EZ templates may require specific preparation steps that depend on the operating system. To prepare, for example, a SLES 15 template for container creation, you additionally need to do the following:.
To create a container, use the prlctl create command as follows:. If you want to create a container with a guest OS different from the default specified in the global configuration file, add the --ostemplate option after the prlctl create command.
To find out where the private area is located, use the prlctl list command as follows:. The first time you install an operating system in a container, its cache is created. To create a cache, you need to have an active Internet connection to access repositories that contain packages for the respective operating system. The specified OS template must be present on the destination server for migration to be successful.
To skip all validation checks, indicate the --force option. The root account is used to log in to the remote server by default, so you will be asked for the root password. Note that migrating EZ templates always copies them to a remote server.
If the source EZ template is not needed after migration, you can manually delete it with the prlsrvctl cttemplate remove command.
After migration, you can check that the migrated EZ templates are present on the destination server with the prlsrvctl cttemplate list command:.
The name of the Linux distribution for which the EZ template is created. Contains native CentOS 7 distribution kernel version. Specifies the packaging system used to handle the EZ template. Scripts that are executed before and after the packages in the EZ template are installed on the hardware node.
Scripts that are executed before and after updating packages inside the container. To share a custom EZ template between hardware nodes, you can create an RPM package with it as follows:. Edit the template according to your needs, e. Build the RPM from the. Do not build more than one template at once. Prev Next Virtuozzo Hybrid Server offers several ways to create customized containers with preinstalled applications: From a golden image an OS EZ template cache with preinstalled application templates.
From a custom OS EZ template that specifies a custom application package list. From a custom configuration sample file that specifies custom application EZ templates.
The best way to create such a cache is: Make a custom sample configuration file with information on the OS EZ template to cache and application EZ templates to preinstall. Note If you already have a custom sample configuration file with application EZ templates specified in it, you can reuse it instead of creating a new one.
0コメント