Article ID: 117483, created on Sep 25, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux 4.7


I have run apt-get dist-upgrade inside my container and restarted it. After that the container is not operable:

# vzctl enter 111
enter into CT 111 failed
Unable to open pty: No such file or directory

# vzctl exec 111 ps ax
    1 ?        Rs     0:16 init boot     
    2 ?        S      0:00 [kthreadd/1020]
    3 ?        S      0:00 [khelper/1020]
   29 ?        Rs     0:00 ps ax


The reason is that the package upstart which manages the system and services start in the container was replaced with sysvinit:

root@debian7testi2:~# apt-get dist-upgrade
The following packages will be REMOVED:
The following NEW packages will be installed:
  e2fsprogs libss2 sysvinit
0 upgraded, 3 newly installed, 1 to remove and 0 not upgraded.
Need to get 1176 kB of archives.
After this operation, 1646 kB of additional disk space will be used.

It is Debian issue, for more information you can refer to:

bug 525141

bug 561627


To avoid this issue, use apt-get update or aptitude full-upgrade instead of apt-get dist-upgrade.

And in order to fix containers which are already broken, install the package upstart back as in the example below and restart the container:

~# echo 'Yes, do as I say!' | vzpkg install CTID -p upstart -- --force-yes
~# vzctl restart CTID

(Replace CTID with the actual container's ID value of the broken container.)

The problem has been permanenty fixed in Debian 7.0 EZ templates version debian-7.0-x86_64-ez-4.7.0-4.noarch.rpm and debian-7.0-x86-ez-4.7.0-3.noarch.rpm (check this article for release notes).

To avoid the issue for any future Debian containers, update Debian 7.0 EZ OS template installed on the node and recreate the template cache using the following commands:

# vzpkg update metadata debian-7.0-x86_64 -r
# vzpkg create cache debian-7.0-x86_64 -f
# vzpkg update metadata debian-7.0-x86 -r
# vzpkg create cache debian-7.0-x86 -f

To identify containers based on Debian 7.0 x64 which can potentially face this problem, execute the following command for each Debian 7.0 container:

# vzctl exec CTID dpkg --print-foreign-architectures

If there is no output, please execute the following command for the container:

# vzctl exec CTID dpkg --add-architecture i386

Search Words

container only 3 proc






containert only 3 proc

4 processes

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF