User Guide/Operations on Containers - Revision history

Kir: fix man page link

2015-09-01T20:53:45Z

fix man page link

Nathan Reese: /* Setting root Password for Container */

2014-02-11T22:16:15Z

‎Setting root Password for Container

88.76.30.157: /* Standard (offline) migration */

2011-09-29T14:36:43Z

‎Standard (offline) migration

88.76.30.157: /* Standard (offline) migration */

2011-09-29T14:35:00Z

‎Standard (offline) migration

193.152.163.57: /* Standard (offline) migration */

2010-11-10T10:56:26Z

‎Standard (offline) migration

Kir: /* Running Commands in Container */ filled in

2009-04-28T11:22:07Z

‎Running Commands in Container: filled in

Kir: /* Suspending Container */ filled in

2009-04-28T11:09:23Z

‎Suspending Container: filled in

Kir: /* Disabling Container */ filled in

2009-04-28T10:56:49Z

‎Disabling Container: filled in

Kir: /* Deleting Container */ fixed example

2009-04-28T10:52:06Z

‎Deleting Container: fixed example

Kir: /* Listing Containers */ no more FIXME

2009-04-27T17:00:59Z

‎Listing Containers: no more FIXME

@@ Line 439: / Line 439: @@
 During the command execution, the <code>/vz/dump/Dump.101</code> file containing the entire state of Container 101 is created and the Container itself is stopped.
-Note: You can set another directory to store dump files for your Containers by changing the value of the DUMPDIR parameter in the OpenVZ global file. Detailed information on the OpenVZ global file and the parameters you can specify in it is provided in the {{man|vz|5}}.
+Note: You can set another directory to store dump files for your Containers by changing the value of the DUMPDIR parameter in the OpenVZ global file. Detailed information on the OpenVZ global file and the parameters you can specify in it is provided in the {{man|vz.conf|5}}.
 At any time, you can resume Container 101 by executing the following command:

@@ Line 143: / Line 143: @@
   # '''vzctl set 101 --userpasswd root:test'''
-In this example, we set the root password for Container 101 to "test", and you can log in to the Container via SSH as root and administer it in the same way as you administer a standalone Linux server: install additional software, add users, set up services, and so on. The password will be set inside the Container in the <code>/etc/shadow</code> file in an encrypted form and will not be stored in the Container configuration file. Therefore, if you forget the password, you have to reset it. Note that <code>--userpasswd</code> ignores the <code>--save</code> switch, the password is anyway persistently set for the given Container.
+In this example, we set the root password for Container 101 to "test", and you can log in to the Container via SSH as root and administer it in the same way as you administer a standalone Linux server: install additional software, add users, set up services, and so on. The password will be set inside the Container in the <code>/etc/shadow</code> file in an encrypted form and will not be stored in the Container configuration file. Therefore, if you forget the password, you have to reset it. Note that <code>--userpasswd</code> ignores the <code>--save</code> switch, the password is persistently set for the given Container.
 While you can create users and set passwords for them using the <code>vzctl exec</code> or <code>vzctl set</code> commands, it is suggested that you delegate user management to the Container administrator advising him/her of the Container root account password.

@@ Line 343: / Line 343: @@
 # The Container on the Destination Node is started.
-'''WARNING: By default, after the migration process is completed, the Container private area and configuration file are removed on the Source Node!''' However, if you wish the Container private area on the Source Node to not be removed after the successful Container migration, you can override the default <code>vzmigrate</code> behavior by using the <code>–r no</code> switch.
+'''WARNING: By default, after the migration process is completed, the Container private area and configuration file are deleted on the Source Node!''' However, if you wish the Container private area on the Source Node to not be removed after the successful Container migration, you can override the default <code>vzmigrate</code> behavior by using the <code>–r no</code> switch.
 There is a short downtime needed to stop the Container on the Source Node, copy the Container private data changes to the Destination Node, and start the Container on the Destination Node. However, this time is very short and does not usually exceed one minute.

@@ Line 343: / Line 343: @@
 # The Container on the Destination Node is started.
 There is a short downtime needed to stop the Container on the Source Node, copy the Container private data changes to the Destination Node, and start the Container on the Destination Node. However, this time is very short and does not usually exceed one minute.
@@ Line 357: / Line 358: @@
 {{Note|For the command to be successful, a direct SSH connection (on port 22) should be allowed between the Source and Destination Nodes.}}
 === Zero-downtime (online) migration ===

@@ Line 358: / Line 358: @@
 {{Note|For the command to be successful, a direct SSH connection (on port 22) should be allowed between the Source and Destination Nodes.}}
-By default, after the migration process is completed, the Container private area and configuration file are removed on the Source Node. However, if you wish the Container private area on the Source Node to be removed after the successful Container migration, you can override the default <code>vzmigrate</code> behavior by using the <code>–r no</code> switch.
+By default, after the migration process is completed, the Container private area and configuration file are removed on the Source Node. However, if you wish the Container private area on the Source Node to not be removed after the successful Container migration, you can override the default <code>vzmigrate</code> behavior by using the <code>–r no</code> switch.
 === Zero-downtime (online) migration ===

← Older revision		Revision as of 11:22, 28 April 2009
Line 465:		Line 465:

	== Running Commands in Container ==		== Running Commands in Container ==
		+
		+	Usually, a Container administrator logs in to the Container via network and executes any commands in the Container as on any other Linux box. However, you might need to execute commands inside Containers bypassing the normal login sequence. This can be helpful if:
		+
		+	* You do not know the Container login information, and you need to run some diagnosis commands inside the Container in order to verify that it is operational.
		+	* Network access is absent for a Container. For example, the Container administrator might have accidentally applied incorrect firewalling rules or stopped the SSH daemon.
		+
		+	The OpenVZ software allows you to execute commands in a Container in these cases. Use the <code>vzctl exec</code> command for running a command inside the Container with the given ID. The session below illustrates the situation when the SSH daemon is not started:
		+
		+	# '''vzctl exec 103 /etc/init.d/sshd status'''
		+	openssh-daemon is stopped
		+	# '''vzctl exec 103 /etc/init.d/sshd start'''
		+	Starting sshd: [ OK ]
		+	# '''vzctl exec 103 /etc/init.d/sshd status'''
		+	openssh-daemon (pid 9899) is running...
		+
		+	Now Container users can log in to the Container via SSH (assuming that networking and firewall are not misconfigured).
		+
		+	When executing commands inside a Container from shell scripts, use the <code>vzctl exec2</code> command. It has the same syntax as <code>vzctl exec</code> but returns the exit code of the command being executed instead of the exit code of <code>vzctl</code> itself. You can check the exit code to find out whether the command has completed successfully.
		+
		+	If you wish to execute a command in all running Containers, you can use the following script:
		+
		+	# '''for CT in $(vzlist -H -o ctid); do echo "== CT $CT =="; vzctl exec $CT ''command''; done'''
		+
		+	where ''<code>command</code>'' is the command to be executed in all the running Containers. For example:
		+
		+	# '''for CT in $(vzlist -H -o ctid); do echo "== CT $CT =="; vzctl exec $CT uptime; done'''
		+	== CT 103 ==
		+	15:17:19 up 13 min, 0 users, load average: 0.00, 0.00, 0.00
		+	== CT 123123123 ==
		+	15:17:19 up 22:00, 0 users, load average: 0.00, 0.00, 0.00

	<noinclude>{{UG/Footer}}</noinclude>		<noinclude>{{UG/Footer}}</noinclude>

@@ Line 425: / Line 425: @@
 == Suspending Container ==
 == Running Commands in Container ==
 <noinclude>{{UG/Footer}}</noinclude>

@@ Line 382: / Line 382: @@
 You can delete a Container that is not needed anymore with the <code>vzctl destroy ''CTID''</code> command. This command removes the Container private area completely and renames the Container configuration file and action scripts by appending the <code>.destroyed</code> suffix to them.
-{{Note|Since vzctl-3.0.24, you can also use the vzctl delete command introduced in Virtuozzo Containers 4.0 to remove Containers from your Hardware Node. This command has the syntax identical to vzctl destroy and is meant to replace the latter in the future.}}
+{{Note|Since vzctl-3.0.24, you can also use the <code>vzctl delete</code> command introduced in Virtuozzo Containers 4.0 to remove Containers from your Hardware Node. This command has the syntax identical to vzctl destroy and is meant to replace the latter in the future.}}
 A running Container cannot be destroyed with the <code>vzctl destroy</code> command. The example below illustrates destroying Container 101:
-# vzctl destroy 101
+ # '''vzctl destroy 101'''
-Destroying Container private area: /vz/private/101
+If you do not need the backup copy of the Container configuration files (with the .destroyed suffix), you may delete them manually.
 == Disabling Container ==
 == Suspending Container ==

← Older revision		Revision as of 17:00, 27 April 2009
Line 241:		Line 241:

	This shows only running Containers with the information about their IDs and soft limit on disk inodes (see the {{UG/Chapter link\|Managing Resources}} chapter for more information), with the list sorted by this soft limit. The full list of the <code>vzlist</code> command line switches and output and sorting options is available in the {{man\|vzlist\|8}} man page.		This shows only running Containers with the information about their IDs and soft limit on disk inodes (see the {{UG/Chapter link\|Managing Resources}} chapter for more information), with the list sorted by this soft limit. The full list of the <code>vzlist</code> command line switches and output and sorting options is available in the {{man\|vzlist\|8}} man page.
−
−	~~FIXME~~

	== Setting Name for Container ==		== Setting Name for Container ==