VNC container fails to start if `x11` volume is in corrupt state

[cooperj]

• When starting the VNC container or restarting the compose file, the x11 volume can become corrupt and make it unable to launch
• Checks need to be implemented to see if that is causing an issue starting the service
• If it has failed, automatically recover (potentially by clearing or reseting the volume)
• Improve logging to let the developer know why it has gone wrong and tell them about the issue.