singularity(1)

NAME

singularity-test - Run the user-defined tests within a container

SYNOPSIS

singularity test [exec options...]

DESCRIPTION

The 'test' command allows you to execute a testscript (if available) inside of
  a given container

NOTE:
      For instances if there is a daemon process running inside the container,
      then subsequent container commands will all run within the same
      namespaces. This means that the --writable and --contain options will not
      be honored as the namespaces have already been configured by the
      'singularity start' command.

OPTIONS

--add-caps=""
    a comma separated capability list to add

--allow-setuid[=false]
    allow setuid binaries in container (root only)

--app=""
    set an application to run inside a container

--apply-cgroups=""
    apply cgroups from file for container processes (root only)

-B, --bind=[]
    a user-bind path specification. spec has the format src[:dest[:opts]], where src and dest are outside and inside paths. If dest is not given, it is set equal to src. Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which is the default). Multiple bind paths can be given by a comma separated list.

-e, --cleanenv[=false]
    clean environment before running container

-c, --contain[=false]
    use minimal /dev and empty other directories (e.g. /tmp and $HOME) instead of sharing filesystems from your host

-C, --containall[=false]
    contain not only file systems, but also PID, IPC, and environment

--disable-cache[=false]
    dont use cache, and dont create cache

--dns=""
    list of DNS server separated by commas to add in resolv.conf

--docker-login[=false]
    login to a Docker Repository interactively

--drop-caps=""
    a comma separated capability list to drop

--env=[]
    pass environment variable to contained process

--env-file=""
    pass environment variables from file to contained process

-f, --fakeroot[=false]
    run container in new user namespace as uid 0

--fusemount=[]
    A FUSE filesystem mount specification of the form ': ' - where is 'container' or 'host', specifying where the mount will be performed ('container-daemon' or 'host-daemon' will run the FUSE process detached). is the path to the FUSE executable, plus options for the mount. is the location in the container to which the FUSE mount will be attached. E.g. 'container:sshfs 10.0.0.1:/ /sshfs'. Implies --pid.

-h, --help[=false]
    help for test

-H, --home="/build"
    a home directory specification. spec can either be a src path or src:dest pair. src is the source path of the home directory outside the container and dest overrides the home directory within the container.

--hostname=""
    set container hostname

-i, --ipc[=false]
    run container in a new IPC namespace

--keep-privs[=false]
    let root user keep privileges in container (root only)

-n, --net[=false]
    run container in a new network namespace (sets up a bridge network interface by default)

--network="bridge"
    specify desired network type separated by commas, each network will bring up a dedicated interface inside container

--network-args=[]
    specify network arguments to pass to CNI plugins

--no-home[=false]
    do NOT mount users home directory if /home is not the current working directory

--no-init[=false]
    do NOT start shim process with --pid

--no-mount=[]
    disable one or more mount xxx options set in singularity.conf

--no-privs[=false]
    drop all privileges from root user in container)

--no-umask[=false]
    do not propagate umask to the container, set default 0022 umask

--nohttps[=false]
    do NOT use HTTPS with the docker:// transport (useful for local docker registries without a certificate)

--nonet[=false]
    disable VM network handling

--nv[=false]
    enable experimental Nvidia support

-o, --overlay=[]
    use an overlayFS image for persistent data storage or as read-only layer of container

--passphrase[=false]
    prompt for an encryption passphrase

--pem-path=""
    enter an path to a PEM formated RSA key for an encrypted container

-p, --pid[=false]
    run container in a new PID namespace

--pwd=""
    initial working directory for payload process inside the container

--rocm[=false]
    enable experimental Rocm support

-S, --scratch=[]
    include a scratch directory within the container that is linked to a temporary dir (use -W to force location)

--security=[]
    enable security features (SELinux, Apparmor, Seccomp)

-u, --userns[=false]
    run container in a new user namespace, allowing Singularity to run completely unprivileged on recent kernels. This disables some features of Singularity, for example it only works with sandbox images.

--uts[=false]
    run container in a new UTS namespace

--vm[=false]
    enable VM support

--vm-cpu="1"
    number of CPU cores to allocate to Virtual Machine (implies --vm)

--vm-err[=false]
    enable attaching stderr from VM

--vm-ip="dhcp"
    IP Address to assign for container usage. Defaults to DHCP within bridge network.

--vm-ram="1024"
    amount of RAM in MiB to allocate to Virtual Machine (implies --vm)

-W, --workdir=""
    working directory to be used for /tmp, /var/tmp and $HOME (if -c/--contain was also used)

-w, --writable[=false]
    by default all Singularity containers are available as read only. This option makes the file system accessible as read/write.

--writable-tmpfs[=false]
    makes the file system accessible as read-write with non persistent data (with overlay support only)

EXAMPLE

      Set the '%test' section with a definition file like so:
      %test
          echo "hello from test" "$@"
      $ singularity test /tmp/debian.sif command
          hello from test command
      For additional help, please visit our public documentation pages which are
      found at:
          https://www.sylabs.io/docs/

SEE ALSO

singularity(1)

HISTORY

9-Feb-2022 Auto generated by spf13/cobra