On Wed, Sep 20, 2017 at 09:29:09AM +0100, Hunt, James O wrote:
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:
However, we recently added stateless  support to cc-runtime . 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:
To be more clear:
If you want to modify any configuration from Clear Containers
and modify as you want the file located in /etc
Please do not touch
as this file will be package/vendor provided, and files in /etc
are reserved for local administrator.
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 .
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
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.
 - https://clearlinux.org/features/stateless
 - https://github.com/clearcontainers/runtime/pull/564
 - 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
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3
cc-devel mailing list
Miguel Bernal Marin Open Source Technology Center