|
|
|
|
A Container may be started up, restarted, and shut down like an ordinary computer. Depending on the Container state, only those operations are accessible that comply with its current state. For example, a running Container cannot be started for obvious reasons, and so on. The following Container states can be characterized as stable:
Status |
Description |
Running |
The Container is running; therefore, it may only be restarted or stopped. |
Down |
The Container is stopped; therefore, it may only be started. |
|
The Container is being repaired. You cannot perform any action on the Container until you click the Finish Repair button on the Start Container in Repair Mode page. |
Besides these states, during Container operations a Container may be in one of the transitional states: mounting, starting, stopping, etc. When in a transitional state, you cannot perform any action on the Container until the operation is finished. The description of all possible Container statuses is provided in the Container Statuses section.
Click the Start Container, Stop Container, or Restart Container button to perform the corresponding action. On clicking one of these buttons, this action is logged.
If you are managing a Container residing on the Hardware Node with the Linux operating system installed and wish to stop your Container, bear in mind that there is a two-minute timeout for the Container shutdown scripts to be executed. If the Container is not stopped in two minutes, the system forcibly kills all the processes in the Container. The Container will be stopped in any case, even if it is seriously damaged. To avoid waiting for two minutes if you are operating a Container that is known to be corrupt, you may use the Power Off link that is situated in the Tasks section of the Container dashboard.
