OpenVZ Forum


Home » General » Support » Unable to Create Container (container create)
Unable to Create Container [message #52154] Tue, 25 August 2015 03:09 Go to next message
krazybob is currently offline  krazybob
Messages: 38
Registered: December 2009
Location: Los Angeles, CA
Member
I am not able to create containers on centos 7. Centos7 with openz uses:

prlctl create 101 --ostemplate centos-7-x86_64 --vmtype ct

however it fails to create every time.

The servers base OS is CentOS 7 64-bit.
Re: Unable to Create Container [message #52156 is a reply to message #52154] Tue, 25 August 2015 08:30 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

please post the output of prlctl create included error as well
Re: Unable to Create Container [message #52161 is a reply to message #52156] Tue, 25 August 2015 17:02 Go to previous messageGo to next message
krazybob is currently offline  krazybob
Messages: 38
Registered: December 2009
Location: Los Angeles, CA
Member
Thank you for the help.

So I am running into this issue:

http://superuser.com/questions/937023/openvz-fails-on-contai ner-create-unable-to-get-appcache-tarball-name

Here is the screenshot:

https://gyazo.com/7c055eced7cbdd4293b0bc66e40ee558
Re: Unable to Create Container [message #52162 is a reply to message #52161] Wed, 26 August 2015 07:35 Go to previous messageGo to next message
krazybob is currently offline  krazybob
Messages: 38
Registered: December 2009
Location: Los Angeles, CA
Member
We tried rolling back to CentOS 6 for the container...

[root@hw001 cache]# prlctl create 101 --ostemplate centos-6-x86_64-minimal --vmtype ct
Creating the Virtuozzo Container...
Failed to register the CT: Operation failed. Unable to get appcache tarball name for f4cafbc9-2102-4519-944e-a5facf772354.conf with ostemplate

We we installed CentOOS 6.7 on the server and had no problems.
Re: Unable to Create Container [message #52163 is a reply to message #52161] Wed, 26 August 2015 08:30 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

Have you install the vzpkg template for centos-7 and create an os cache?

Please post "vzpkg list"
Re: Unable to Create Container [message #52164 is a reply to message #52163] Wed, 26 August 2015 16:08 Go to previous messageGo to next message
krazybob is currently offline  krazybob
Messages: 38
Registered: December 2009
Location: Los Angeles, CA
Member
It shows no output. I am relaying information from the server management company.

Could you pleaase tell me where are the instructions for creating a CentOS 7 64-bit template for container creation? I don't think I'm typing the correct search terms in Google.

I used to have to do this on Virtuozzo years ago and have forgotten the process. The gz's are on the server:

-rw-r--r-- 1 root root 133M Aug 7 04:19 centos-7-x86_64-minimal.tar.gz
-rw-r--r-- 1 root root 203M Aug 7 04:18 centos-7-x86_64.tar.gz

ASs I recall:

Quote:

[root@hw001 ~]# vzpkg create cache centos-7-x86_64
Creating OS template cache for centos-7-x86_64 template
Can not find 'centos-7-x86_64' EZ os template
Some template(s) centos-7-x86_64-ez is not found, running /usr/bin/yum to install it...
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* virtuozzo-os: mirror.supremebytes.com
* virtuozzo-updates: mirror.supremebytes.com
126 packages excluded due to repository priority protections
Package centos-7-x86_64-ez-7.0.0-5.vz7.noarch already installed and latest version
Nothing to do
Can not find 'centos-7-x86_64' EZ os template


Re: Unable to Create Container [message #52165 is a reply to message #52164] Wed, 26 August 2015 17:33 Go to previous messageGo to next message
krazybob is currently offline  krazybob
Messages: 38
Registered: December 2009
Location: Los Angeles, CA
Member
I am dealing with Deer Valley Data and they are doing everything right! They appear to have the most current kernel installed as weell.

[root@hw001 ~]# uname -a
Linux hw001.servers.net 3.10.0-123.1.2.vz7.5.29 #1 SMP Fri Jul 24 18:45:12 MSK 2015 x86_64 x86_64 x86_64 GNU/Linux

or is there an Enterprise kernel that gives me full access to memory - an issue for another time.

Here's the last output.

Quote:

Status: New Tech Update - Wed Aug 26 - 8:53 AM
So I have ensured that the cache has been created here:

[root@hw001 vz]# vzpkg create appcache --ostemplate centos-7-x86_64 --apptemplate devel
Can not find 'centos-7-x86_64' EZ os template
Some template(s) centos-7-x86_64-ez is not found, running /usr/bin/yum to install it...
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* virtuozzo-os: mirror.supremebytes.com
* virtuozzo-updates: mirror.supremebytes.com
126 packages excluded due to repository priority protections
Package centos-7-x86_64-ez-7.0.0-5.vz7.noarch already installed and latest version
Nothing to do
Can not find 'centos-7-x86_64' EZ os template

As you can see it says it is already installed "Package centos-7-x86_64-ez-7.0.0-5.vz7.noarch already installed and latest version"

Then trying to create the container with the basic config:

[root@hw001 vz]# vzctl create 101 --ostemplate centos-7-x86_64 --config basic
Unable to get appcache tarball name for ve-basic.conf-sample with ostemplate centos-7-x86_64
Destroying Container private area: /vz/private/101
Warning: Container is in old data format, unregistration skipped
Container private area was destroyed
Creation of Container private area failed
[root@hw001 vz]#

Also here is the basic config:

[root@hw001 conf]# ls
networks_classes ve-confixx.conf-sample ve-vswap.2048MB.conf-sample ve-vswap.512MB.conf-sample vps.vzpkgtools.conf-sample
ve-basic.conf-sample ve-vswap.1024MB.conf-sample ve-vswap.256MB.conf-sample ve-vswap.plesk.conf-sample

"ve-basic.conf-sample"

Here are its contents:

# This is an example configuration file for so-called "basic" Container.
#<agent>: Configuration file for allocating 256 Mb of memory.
#
# Copyright (c) 1999-2015 Parallels IP Holdings GmbH. All rights reserved.

VERSION="2"

ONBOOT="yes"

PHYSPAGES="65536:65536"
SWAPPAGES="65536"
# Virtual memory overcommitment
# privvmpages = (ram + swap) * VM_OVERCOMMIT (unlimited if not specified)
#VM_OVERCOMMIT="1.5"

CPUUNITS="1000"

NETFILTER="stateless"

DISKSPACE="10485760:10485760"
DISKINODES="655360:655360"

QUOTATIME="0"
IP_ADDRESS="0.0.0.0"

ARCH="x86"
PLATFORM="linux"
Re: Unable to Create Container [message #52166 is a reply to message #52165] Wed, 26 August 2015 18:30 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

i try to repeat the issue:

$ prlsrvctl info | grep -e ^OS
OS: Virtuozzo release 7.0.0 (10.vz7) (3.10.0-123.1.2.vz7.5.29) <--! it the same version like yours

$ rpm -qa | grep centos-7
centos-7-x86_64-ez-7.0.0-5.vz7.noarch

and the vz template is installed under /vz/template/centos/7/...


$ cat /vz/template/centos/7/x86_64/config/os/default/summary <--! are you getting the same output?
Centos 7 (for AMD64/Intel EM64T) Virtuozzo Template

$ vzpkg list | grep ^centos-7
centos-7-x86_64 <--! the empty column indicate that no (os)cache was created
centos-7-x86_64 vzftpd
centos-7-x86_64 spamassassin
centos-7-x86_64 php
centos-7-x86_64 mod_ssl
centos-7-x86_64 postgresql
centos-7-x86_64 tomcat
centos-7-x86_64 devel
centos-7-x86_64 mysql
centos-7-x86_64 cyrus-imap
centos-7-x86_64 mailman
centos-7-x86_64 docker
centos-7-x86_64 jre
centos-7-x86_64 jsdk

$ vzpkg create cache centos-7-x86_64
Creating OS template cache for centos-7-x86_64 template
(...)
OS template centos-7-x86_64 cache was created

After create os cache - install a new ct with that template

$ vzctl create $(uuidgen) --ostemplate centos-7-x86_64
Creating Container private area (centos-7-x86_64) with applications from config (ve-basic.conf-sample)
(...)
Container 78d72ccd-1a30-4459-b856-3eb8cffd6fd2 was successfully registered
Container private area /vz/private/78d72ccd-1a30-4459-b856-3eb8cffd6fd2 created

HTH Thorsten
Re: Unable to Create Container [message #52170 is a reply to message #52166] Thu, 27 August 2015 20:36 Go to previous messageGo to next message
krazybob is currently offline  krazybob
Messages: 38
Registered: December 2009
Location: Los Angeles, CA
Member
We found that the file system of CentOS 7 was not compatible with OpenVZ 7. We had to use EXT4 when installing. After doing that we were able to create containers.

Could you explain why this is? I sure appreciate it. Thank you very much.
Re: Unable to Create Container [message #52171 is a reply to message #52170] Thu, 27 August 2015 20:59 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

the default type for storing the container (ct) data is on/in a ploop device (-> https://wiki.openvz.org/Ploop/Getting_started )
and the reqirements for ploop are the filesystem on which the data is located must be formated with ext4 or use nfsv3

btw have you any log entries found in /var/log/vzctl.log detect some kind of issue?
Re: Unable to Create Container [message #52172 is a reply to message #52171] Thu, 27 August 2015 22:02 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

found an issue:
on vzpkg create a temporary ploop image is create in directory /var/tmp - if underlaying filesystem is not an ext4 this creation failed with this error, too:

(...)
Error: Failed to create ploop image /var/tmp//vzpkg.2GEcRO/cache-private/root.hdd/root.hds: Error in add_delta (ploop.c:1310): Can't add image /var/tmp//vzpkg.2GEcRO/cache-private/root.hdd/root.hds: unsupported underlying filesystem 3
Error: Cannot create ploop device
(...)

HTH Thorsten

[Updated on: Thu, 27 August 2015 22:02]

Report message to a moderator

Re: Unable to Create Container [message #52173 is a reply to message #52172] Thu, 27 August 2015 23:20 Go to previous message
krazybob is currently offline  krazybob
Messages: 38
Registered: December 2009
Location: Los Angeles, CA
Member
You started us looking and that is what we found as well! The documentation to Ploop made it clear that the FS needed to be EXT4. Thank you for the heads up!!!
Previous Topic: yum install failure download.openvz.org/mirrors-current
Next Topic: How to exclude kernel updates in migrated VZ containers?
Goto Forum:
  


Current Time: Fri Apr 19 08:58:52 GMT 2024

Total time taken to generate the page: 0.01834 seconds