6,534
edits
Changes
→Disabling Container: filled in
== Disabling Container ==
There may appear situations when you wish to forbid Container owners to use their Containers. For example, it may happen in case the Container owner uses it for unallowed purposes: intruding into computers of other users, participating in DoS attacks, etc.
In such cases, the OpenVZ software allows you to disable a Container, thus, making it impossible to start the Container once it was stopped. For example, you can execute the following command to disable Container 101 residing on your Hardware Node:
# '''vzctl set 101 --disabled yes --save'''
{{Note|This option makes no sense without the <code>--save</code> flag, so you have to supply it.}}
After the Container stopping, the Container user will not be able to start it again until you enable this Container again by passing the <code>--disabled no</code> option to <code>vzctl set</code>. You can also use the <code>--force</code> option to start any disabled Container. For example:
# '''vzctl start 103'''
Container start disabled
# '''vzctl start 103 --force'''
Starting container ...
Container is mounted
Adding IP address(es): 192.168.16.3
Setting CPU units: 1000
Configure meminfo: 65536
Container start in progress...
== Suspending Container ==
== Running Commands in Container ==
<noinclude>{{UG/Footer}}</noinclude>
