Asciidoc being in the configure log should not cause it to be added to
the build requires automatically. This is also intended to enable
asciidoc to be removed from use entirely.
autospec/failed_commands | 1 -
1 file changed, 1 deletion(-)
diff --git a/autospec/failed_commands b/autospec/failed_commands
index f140397..1a6d6c4 100644
@@ -84,7 +84,6 @@ less, less
It looks like https://github.com/clearlinux-pkgs/linux is a special case for ClearLinux's build automation. Instead of using the Makefile and running autospec I'm guessing you're running something like:
mock -r clear --buildsrpm --sources=./ --spec=linux.spec --uniqueext=linux --result=results/ --no-cleanup-after
mock -r clear --rebuild --uniqueext=linux --result=results/ --no-cleanup-after ./results/linux-4.13.2-390.src.rpm
What does this automation looks like behind the scenes so I can replicate it?
Today, a documentation restructure went live on Clearlinux.org (https://clearlinux.org/documentation/clear-linux/clear-linux.html).
This change improves navigation throughout our docs and make contributing to CL docs easier. Content is now categorized into five sections: Get Started, Concepts, Guides, Tutorials, and Reference. Descriptions on the sections are as follows:
Get Started: Information about installing Clear Linux.
Concepts: Detailed technical information about features.
Guides: Step-by-step instructions to complete common tasks.
Tutorials: Step-by-step instructions to complete the installation and configuration of tools needed for a specific use case.
Reference: Information providing additional context or details.
With this restructure comes URL changes to many existing documents. To ensure continued access, redirects have been applied to all affected URLs and will remain until further notice.
Just one question about isolation of Clear Container.
As we known, Clear Container use vm to provides underlying process
isolation, it indeed makes container be more secure, but I'm thinking if
this is enough for multi-tenant env, for example, image management, if
client A pulls a image, then client B may see the image, actually this is
not allowed in multi-tenant environment.
I also have some concerns about the isolation of network and storage.
So maybe what I'm looking for is an end to end isolation solution to use
clear container in multi-tenant environment, includes the isolation of
network, storage, image and process. :)