LXC container issues

This section contains issues related to LXC containers only.

Issue – A Proxmox node hangs when trying to stop or restart an LXC container

Solution: This has been an issue since the initial release of Proxmox VE 4.0. Owing to a bug when shutdown, stop or restart was initiated for LXC container from GUI, the node itself became unusable and all network connectivity was lost. The only way to come out of it was to reboot the entire node. In consecutive later releases, this issue has been addressed and patched by Proxmox developers. If you are in Proxmox 4.0, an immediate upgrade to 4.1 or later is highly recommended.

Issue – The noVNC console only shows a cursor for LXC containers

Solution: Owing to unknown reasons, the noVNC console may only show a cursor, as shown in the following screenshot, when trying to access an LXC container:

This does not mean that the container is frozen. Simply hit Enter to get to the login prompt.