This repository has been archived by the owner on May 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 70
cc-check should only warn if "unrestricted_guest" is not set when running under a hypervisor #439
Comments
👍 |
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Aug 21, 2017
If running under a hypervisor, the kvm "unrestricted_guest" option is not required. Fixes clearcontainers#439. Signed-off-by: James O. D. Hunt <[email protected]>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Aug 21, 2017
If running under a hypervisor, the kvm "unrestricted_guest" option is not required. Fixes clearcontainers#439. Signed-off-by: James O. D. Hunt <[email protected]>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Aug 21, 2017
If running under a hypervisor, the kvm "unrestricted_guest" option is not required. Fixes clearcontainers#439. Signed-off-by: James O. D. Hunt <[email protected]>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Aug 22, 2017
If running under a hypervisor, the kvm "unrestricted_guest" option is not required. Fixes clearcontainers#439. Signed-off-by: James O. D. Hunt <[email protected]>
mcastelino
pushed a commit
to mcastelino/runtime
that referenced
this issue
Dec 6, 2018
ci: Fix static checks call.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Now that virtcontainers provides a way to detect if running under a hypervisor...
... we need to update
cc-check
to determine more intelligently if the environment is capable of running a Clear Container since although environments like Azure do not provideunrestricted_guest
, it is still possible to run a Clear Container on it.In summary,
cc-check
needs to do the following:unrestricted_guest
is not set (since it does work under Azure for example).unrestricted_guest
is not set (no change to current behaviour).See comments on #422.
The text was updated successfully, but these errors were encountered: