Re: [cc-devel] [Clr-dev] Does Clear Linux require or use the Unrestricted Guests capability?
by Miguel Bernal Marin
Hi Dexuan,
>
> It's from a customer. I don't really know the details. Sorry.
> Currently Hyper-V doesn't support Unrestricted Guests for nested hypervisors (but
> I suppose it would be supported soon) and the customer saw a warning about this
> in the compatibility check script. It looks we can ignore the warning, but I'd like to
> know if there would be any consequence.
>
Currently Clear Containers (CC) 3.0 could be run in Azure platforms, you need
to be sure that the platforms has nested vitalization capable.
Regarding Hyper-V, CC-2.X needs some tweaks to run on top of it, but you
can try with CC-3.0.
Pleas ask to your costumer to try CC-3.0
https://clearlinux.org/blogs/announcing-intel%C2%AE-clear-containers-30
As CC-3.0 is out CC team is deprecating CC-2.X.
--
Regards,
Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation
4 years, 10 months
3.0 pending PRs
by Samuel Ortiz
All,
We're about to release Clear Containers 3.0 and we have one outstanding
PR oending:
- KSM tuning: https://github.com/clearcontainers/proxy/pull/118
And we have another one that we may want to merge as well:
- https://github.com/clearcontainers/runtime/pull/550
We'll be working on those 2 PRs, but please speak up if you believe
some others must be part of 3.0.
Cheers,
Samuel.
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
4 years, 10 months
Change to the location of cc-runtime's configuration file
by Hunt, James O
Hi All,
TL;DR - if you build cc-runtime yourself, you should update to the latest
code, build and install and then "sudo rm -rf /etc/clear-containers/".
= Details =
Previously, the default location for the cc-runtime configuration file was:
/etc/clear-containers/configuration.toml
However, we recently added stateless [1] support to cc-runtime [2]. This
results in two significant changes:
1) It now checks in multiple locations for its configuration file.
2) It changes the default location of the configuration file to:
/usr/share/defaults/clear-containers/configuration.toml
If you are building the runtime yourself, the general advice is to remove
the "/etc/clear-containers/" directory since the old configuration file
location will in fact take precedence over the new one [3].
To see where the runtime will attempt to read its configuration from, there
is a new global option:
$ cc-runtime --cc-show-default-config-paths
/etc/clear-containers/configuration.toml
/usr/share/defaults/clear-containers/configuration.toml
In the example output above, if the runtime finds
"/etc/clear-containers/configuration.toml", that file will be used.
Otherwise it will try to use
"/usr/share/defaults/clear-containers/configuration.toml". If neither file
exists, it will error.
Cheers,
James
---
[1] - https://clearlinux.org/features/stateless
[2] - https://github.com/clearcontainers/runtime/pull/564
[3] - If you do not remove "/etc/clear-containers/configuration.toml" and
we update the master configuration, your old
"/etc/clear-containers/configuration.toml" will be used, masking the newer
"/usr/share/defaults/clear-containers/configuration.toml".
-----
https://clearlinux.org
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3
1RJ.
4 years, 10 months
architecture wiki updates for 3.0
by Ernst, Eric
Hey ya'll,
With Graham's help and some initial feedback from Samuel and Manohar I pushed a first pass of our 3.0 Clear Containers architecture documentation.
Some of this is not fully described and/or not accurate currently (this was pulled as a copy of our 2.1 documentation). I'd like to enlist help from individuals for a few sections:
1. Archana, can you take a look @ the shim section?
2. Carlos, can you take a look @ the proxy section?
3. Samuel, can you look @ runtime section?
When multiple people are editing via web interface, github will tell you that it changed and you should reload once someone commits.
--Eric
4 years, 11 months
