You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
It's possible that we've been asked for shim tokens but never managed to fully start the container for some reason. When the runtime tries to clean up in the error path by calling UnregisterVM, we should make sure we clean up all objects associated with the VM in the proxy struct.
And test it.
The text was updated successfully, but these errors were encountered:
When unregisterVM is called we want to free all the tokens we register
previously, all the tokens should not be valid anymore.
Fixes: clearcontainers#66
Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
When unregisterVM is called we want to free all the tokens we register
previously, all the tokens should not be valid anymore.
Fixes: clearcontainers#66
Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
jcvenegas
added a commit
to jcvenegas/cc-proxy
that referenced
this issue
Aug 21, 2017
When unregisterVM is called we want to free all the tokens we register
previously, all the tokens should not be valid anymore.
Fixes: clearcontainers#66
Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
It's possible that we've been asked for shim tokens but never managed to fully start the container for some reason. When the runtime tries to clean up in the error path by calling UnregisterVM, we should make sure we clean up all objects associated with the VM in the proxy struct.
And test it.
The text was updated successfully, but these errors were encountered: