Charliecloud
  • 1. Installation
    • 1.1. Prequisites
      • 1.1.1. Run time
      • 1.1.2. Build time
      • 1.1.3. Test suite
    • 1.2. Install Docker (build systems only)
      • 1.2.1. Understand the security implications of Docker
        • 1.2.1.1. docker equals root
        • 1.2.1.2. Images can contain bad stuff
        • 1.2.1.3. Containers run as root
        • 1.2.1.4. Docker alters your network configuration
        • 1.2.1.5. Docker installs services
      • 1.2.2. Configuring for a proxy
    • 1.3. Install Charliecloud
      • 1.3.1. Download
      • 1.3.2. Build
      • 1.3.3. Install (optional)
    • 1.4. Test Charliecloud
      • 1.4.1. Build
      • 1.4.2. Run
      • 1.4.3. Examples
      • 1.4.4. Quick and multiple-phase tests
  • 2. Tutorial
    • 2.1. 90 seconds to Charliecloud
    • 2.2. Getting help
    • 2.3. Your first user-defined software stack
      • 2.3.1. Defining your UDSS
      • 2.3.2. Build Docker image
      • 2.3.3. Share image and other standard Docker stuff
      • 2.3.4. Flatten image
      • 2.3.5. Distribute tarball
      • 2.3.6. Unpack tarball
      • 2.3.7. Activate image
    • 2.4. Interacting with the host
      • 2.4.1. Filesystems
      • 2.4.2. Network
      • 2.4.3. User and group IDs
    • 2.5. Installing your own software
      • 2.5.1. Third-party software via package manager
      • 2.5.2. Third-party software compiled from source
      • 2.5.3. Your software stored in the image
      • 2.5.4. Your software stored on the host
    • 2.6. Your first single-node, multi-process jobs
      • 2.6.1. Processes coordinated by host
      • 2.6.2. Processes coordinated by container
      • 2.6.3. Processes coordinated by container using host configuration
    • 2.7. Your first multi-node jobs
      • 2.7.1. Interactive MPI hello world
      • 2.7.2. Non-interactive MPI hello world
      • 2.7.3. Interactive Apache Spark
      • 2.7.4. Non-interactive Apache Spark
  • 3. Help text for executables
    • 3.1. ch-build
    • 3.2. ch-build2dir
    • 3.3. ch-docker2tar
    • 3.4. ch-docker-run
    • 3.5. ch-run
    • 3.6. ch-ssh
    • 3.7. ch-tar2dir
  • 4. VirtualBox appliance
    • 4.1. Install and use the appliance
      • 4.1.1. Configure VirtualBox
      • 4.1.2. Install the appliance
      • 4.1.3. Log in and try Charliecloud
    • 4.2. Build the appliance
      • 4.2.1. Initialize VM
      • 4.2.2. Install CentOS
      • 4.2.3. Configure guest OS
        • 4.2.3.1. Log in
        • 4.2.3.2. Update sudoers
        • 4.2.3.3. Configure proxy
        • 4.2.3.4. Install a decent user environment
        • 4.2.3.5. Configure auto-login on console
        • 4.2.3.6. Upgrade kernel
        • 4.2.3.7. Install Guest Additions
        • 4.2.3.8. Install OpenMPI
      • 4.2.4. Install Docker
        • 4.2.4.1. Install
        • 4.2.4.2. Configure proxy
        • 4.2.4.3. Test
      • 4.2.5. Install Charliecloud
        • 4.2.5.1. Set environment variables
        • 4.2.5.2. Enable a second getty
        • 4.2.5.3. Build and install Charliecloud
        • 4.2.5.4. Prime Docker cache
      • 4.2.6. Create export snapshot
      • 4.2.7. Finish testing Charliecloud
      • 4.2.8. Export appliance
    • 4.3. Upgrade the appliance
      • 4.3.1. OS packages via yum
      • 4.3.2. Charliecloud
      • 4.3.3. Docker images
  • 5. Frequently asked questions (FAQ)
    • 5.1. My app needs to write to /var/log, /run, etc.
    • 5.2. Tarball build fails with “No command specified”
    • 5.3. --uid 0 lets me read files I can’t otherwise!
    • 5.4. Why is /bin being added to my $PATH?
    • 5.5. How does setuid mode work?
    • 5.6. ch-run fails with “can’t re-mount image read-only”
    • 5.7. Which specific sudo commands are needed?
  • 6. Copyright and license
 
Charliecloud
  • Docs »
  • 6. Copyright and license

6. Copyright and license¶

Charliecloud is copyright © 2014–2017 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. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

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.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Previous

© Copyright 2014–2017, Los Alamos National Security, LLC.