Provided by: charliecloud_0.9.10-1_amd64 bug

NAME

       charliecloud - Lightweight user-defined software stacks for high-performance computing

WHAT IS CHARLIECLOUD?

       Charliecloud  provides  user-defined software stacks (UDSS) for high-performance computing (HPC) centers.
       This “bring your own software stack” functionality addresses needs such as:

       • software  dependencies  that  are  numerous,  complex,  unusual,  differently  configured,  or   simply
         newer/older than what the center provides;

       • build-time requirements unavailable within the center, such as relatively unfettered internet access;

       • validated software stacks and configuration to meet the standards of a particular field of inquiry;

       • portability  of  environments  between resources, including workstations and other test and development
         system not managed by the center;

       • consistent environments, even archivally so, that can be easily, reliabily, and  verifiably  reproduced
         in the future; and/or

       • usability and comprehensibility.

HOW DOES IT WORK?

       Charliecloud  uses  Linux  user namespaces to run containers with no privileged operations or daemons and
       minimal configuration changes on center resources.  This simple approach avoids most security risks while
       maintaining access to the performance and functionality already on offer.

       Container images can be built using Docker or anything else that can generate a standard Linux filesystem
       tree.

HOW DO I LEARN MORE?

       • Documentation: https://hpc.github.io/charliecloud

       • GitHub repository: https://github.com/hpc/charliecloud

       • We wrote an article for USENIX’s magazine ;login: that explains  in  more  detail  the  motivation  for
         Charliecloud       and       the       technology       upon       which       it       is       based:
         https://www.usenix.org/publications/login/fall2017/priedhorsky

       • A more technical resource is our Supercomputing 2017 paper: https://dl.acm.org/citation.cfm?id=3126925

WHO IS RESPONSIBLE?

       The core Charliecloud team at Los Alamos is:

       • Reid Priedhorsky <reidpr@lanl.gov>, co-founder and BDFL

       • Tim Randles <trandles@lanl.gov>, co-founder

       • Michael Jennings <mej@lanl.gov>

       • Jordan Ogas <jogas@lanl.gov>

       Patches (code, documentation, etc.) contributed by:

       • Reid Priedhorsky <reidpr@lanl.gov>

       • Rusty Davis <rustyd@lanl.gov>

       • Oliver Freyermuth <o.freyermuth@googlemail.com>

       • Christoph Junghans <junghans@lanl.gov>

       • Jordan Ogas <jogas@lanl.gov>

       • Matthew Vernon <mv3@sanger.ac.uk>

       • Peter Wienemann <wienemann@physik.uni-bonn.de>

       • Lowell Wofford <lowell@lanl.gov>

HOW CAN I PARTICIPATE?

       Questions, comments, feature requests, bug reports, etc. can be directed to:

       • our mailing list: charliecloud@groups.io or https://groups.io/g/charliecloud

       • issues on GitHub

       Patches are much appreciated on the software itself as well as documentation.  Optionally, please include
       in your first patch a credit for yourself in the list above.

       We are friendly and welcoming of diversity on all dimensions.

COPYRIGHT AND LICENSE

       Charliecloud is copyright © 2014–2018 Los Alamos National Security, LLC. This software has been  approved
       for open source release, LA-CC 14-096.

       Licensed  under  the Apache License, Version 2.0 (the “License”); you may not use this software except in
       compliance with the License. A copy of the license is included in file LICENSE.

       This material was produced under U.S. Government  contract  DE-AC52-06NA25396  for  Los  Alamos  National
       Laboratory  (LANL),  which  is  operated  by Los Alamos National Security, LLC for the U.S. Department of
       Energy. The U.S. Government has rights to use, reproduce,  and  distribute  this  software.  NEITHER  THE
       GOVERNMENT  NOR  LOS ALAMOS NATIONAL SECURITY, LLC MAKES ANY WARRANTY, EXPRESS OR IMPLIED, OR ASSUMES ANY
       LIABILITY FOR THE USE OF THIS SOFTWARE. If  software  is  modified  to  produce  derivative  works,  such
       modified software should be clearly marked, so as not to confuse it with the version available from LANL.

   Reporting bugs
       If  Charliecloud  was  obtained  from  your  Linux  distribution,  use  your distribution’s bug reporting
       procedures.

       Otherwise, report bugs to: <https://github.com/hpc/charliecloud/issues>

SEE ALSO

       ch-build(1), ch-build2dir(1), ch-docker2tar(1),  ch-pull2dir(1),  ch-pull2tar(1),  ch-run(1),  ch-ssh(1),
       ch-tar2dir(1)

       Full documentation at: <https://hpc.github.io/charliecloud>

NOTE

       These man pages are for Charliecloud version 0.9.10 (Git commit ).

AUTHOR

       Reid Priedhorsky, Tim Randles, and others

COPYRIGHT

       2014–2018, Los Alamos National Security, LLC

                                   2019-09-08 18:23 Coordinated Universal Time                   CHARLIECLOUD(1)