• Login
    • Report A Bug
    • System Information
    • System Tests
    • System Policies
    • Code Documentation
    • Occam Source Code
    • Web Client Source Code
    • About Occam
    • Acknowledgements
    • Guides / Documentation
    • Publications

translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
singularity-environment
    Linux
    QmZdi2nN7zzX6UL314BP1bPPDzTpZySTyCmvMFtxiuBF6T
    5dsx3FGTunNFLbPN2s7N8HBXFAQLnZ
      QmZdi2nN7zzX6UL314BP1bPPDzTpZySTyCmvMFtxiuBF6T
      5dsx3FGTunNFLbPN2s7N8HBXFAQLnZ

      • Details
      • Run
      • Files
      • History
        • Summary

          This provides the basic initialization environment for a Linux object in Occam using the Singularity container engine.

          Environment

          singularity

          Architecture

          x86-64

          Related

          • maintainer

            occam

          RequiresHelp

          This section shows a list of services the current object requests in order to function.

          Services are external resources or APIs that an artifact might need to exist in the environment that are not direct dependencies. It is a little confusing, but these are generally network-accessed resources such as an internet connection or an information service accessed by a network port such as a database.

          For instance, artifacts typically do not have a network. To add network access, you would have to add that as a required service.

          Other 'services' might be hardware, such as particular GPUs or other sub-devices that make sense for the environment of the artifact. This might limit the available deployment targets, however, so some care should be taken to only add required services when they are truly needed.

          You can mark a service as optional if you want to still be able to run even in the absence of the service. You can mark a service as if-needed to hint that the service should only be added if a dependency requires it. Finally, to only run this artifact in the presence of the service, you can mark it as required.

          • service

            nvidia-driver

            if-needed

          • service

            network

            if-needed

          RunHelp

          This section tracks information useful to describing how to run this object.

          Command

          • /occam/init/ld-linux-x86-64.so.2
          • --library-path
          • /occam/init/usr/lib
          • /occam/init/python/bin/python
          • /occam/init/init.py

          Run Environment

          • singularity
          • x86-64

          InstallationHelp

          Objects have a set of files that comprise that object, as seen in the Files tab. When an object is built, they have a set of files that are the result of that build. In each case, these sets of files are the ones that are accessible within a virtual machine when running the object.

          This section describes how those files are accessible and visible to that machine. When a virtual machine is created, the data is always accessible read-only within a particular mounted directory. However, applications may expect to be located at particular directories. This section allows one to place files in different directories when the virtual machine is launched.

          There are two types of access. One is a link where the file is not copied from its original location. Instead, it creates what is called a symbolic link which is a "shortcut" that acts like a normal file but allows the actual data to be in a different directory. The other type is a traditional copy which copies the data explicitly to the provided destination. This takes more time, but the copy can be modified, unlike the read-only link type.

          ActionSourceDestinationSummary
          Linkoccam/init/busybox/bin/sh

          N/A

          Copyetc/etc

          N/A

          No files will be installed.

          Share

          • URL

            Copy
          • Embed Link

            Copy
          • QR Code

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        Confirm
        Do you wish to proceed?

        Confirm message?