Revert "Fix potentially unclosed file in runtimeVM#CreateContainer"
Revert "Fix potentially unclosed file in runtimeVM#CreateContainer"

This reverts commit 924a8e9830f112821f03984d417f938f945ba442, as the
commit in question introduced a regression on CRI-O, when using the VM
runtime type.

After the faulty commit was introduced commit, the following file is
always empty:
`/var/log/pods/$namespace_$pod_name_$pod_uid/$container_name/$restart_number.log`

This commit reverts the faulty one, getting CRI-O back to a state where
the logs are stored in a wrong format, but at least present.

Fixes: https://github.com/cri-o/cri-o/issues/4081

Signed-off-by: Fabiano Fidêncio <2931bae082ef9bc04523ba759c03a4778316d48f@redhat.com>

kubernetes-incubator/ocid,nalind/cri-o,kubernetes-incubator/cri-o,kubernetes-incubator/cri-o,nalind/cri-o,kubernetes-incubator/cri-o,kubernetes-incubator/cri-o,kubernetes-incubator/ocid,kubernetes-incubator/ocid,nalind/cri-o