Repairing Container

Repairing a Container is another way to solve problems with the Container functioning. In Virtuozzo Containers terminology, the Container is mounted in the repair mode. This means that a new Container is temporarily created from scratch with the same network and other parameters as the broken Container, and the root directory of the broken Container is mounted as /repair into the newly-created Container. Thereafter, the administrator is supposed to connect to the new Container via ssh or Parallels Infrastructure Manager file manager using the network and login parameters of the broken Container, go to the /repair directory, and perform one of the following actions:

1. Find the personal data that needs to be saved and copy it to a safe location elsewhere. Do not copy your personal data directly into your new Container, as it will be destroyed once you exit the repair mode. After quitting the repair mode, the broken Container can be reinstalled and the personal data can further be loaded into it from the place where you have saved them.
2. Identify the source of the problem and manually correct it. This method can be recommended to advanced Container administrators, as it presupposes some technical expertise. And it is still recommended to save first your personal data in a safe location, just in case something goes wrong.

Note: When working inside the Container being repaired by means of the Parallels Infrastructure Manager file manager, the file manager root directory (/) corresponds to the /repair directory of the temporary Container, in other words, it represents the root directory of the problem Container, not that of the newly-created one.

Pressing the Start Repair button on the Repair Container screen mounts the Container in the repair mode. It is not necessary to stop the Container beforehand; if the Container is running at the moment of pressing the Start Repair button, it will be first automatically stopped. The description of all possible Container statuses is provided in the Container Statuses section.

When the page is refreshed after pressing the Start Repair button, click the Details link at the end of the The Container has been scheduled to start in the repair mode message to see if the repair mode has been successfully entered. Once the Container enters the repair mode, connect to the new Container via ssh or Parallels Infrastructure Manager file manager and do what you deem reasonable inside the Container. After closing your ssh session, press the Repair link on the Container dashboard once again and press the Finish Repair button to exit the repair mode. After the repair mode is exited, the broken Container starts running, and you may check the repairing effect.

Please send us your feedback on this help page