VGC docker fix for receiving signals

VGC was not receiving signals due to incorrect way of spawning the docker image. VGC was being spawned from a script instead of being spawned as a container directly from the deployment.yaml. 
When spawned from a script, the script will be running as PID 1 and VGC will be the child process. Due to this VGC will not be able to catch OS signals as the signals are directed to PID 1.

Running the VGC container from the deployment.yaml results in VGC to run as PID 1, which allows it to catch signals.