Switch to github.com/golang/dep for vendoring

Signed-off-by: Mrunal Patel <mrunalp@gmail.com>

vendor/github.com/opencontainers/runc/man/README.md

@@ -0,0 +1,11 @@
+runc man pages
+====================
+
+This directory contains man pages for runc in markdown format.
+
+To generate man pages from it, use this command
+
+    ./md2man-all.sh
+
+You will see man pages generated under the man8 directory.
+

vendor/github.com/opencontainers/runc/man/md2man-all.sh

@@ -0,0 +1,22 @@
+#!/bin/bash
+set -e
+
+# get into this script's directory
+cd "$(dirname "$(readlink -f "$BASH_SOURCE")")"
+
+[ "$1" = '-q' ] || {
+	set -x
+	pwd
+}
+
+for FILE in *.md; do
+	base="$(basename "$FILE")"
+	name="${base%.md}"
+	num="${name##*.}"
+	if [ -z "$num" -o "$name" = "$num" ]; then
+		# skip files that aren't of the format xxxx.N.md (like README.md)
+		continue
+	fi
+	mkdir -p "./man${num}"
+	go-md2man -in "$FILE" -out "./man${num}/${name}"
+done

vendor/github.com/opencontainers/runc/man/runc-checkpoint.8.md

@@ -0,0 +1,22 @@
+# NAME
+   runc checkpoint - checkpoint a running container
+
+# USAGE
+   runc checkpoint [command options] <container-id>
+
+Where "<container-id>" is the name for the instance of the container to be
+checkpointed.
+
+# DESCRIPTION
+   The checkpoint command saves the state of the container instance.
+
+# OPTIONS
+   --image-path                 path for saving criu image files
+   --work-path                  path for saving work files and logs
+   --leave-running              leave the process running after checkpointing
+   --tcp-established            allow open tcp connections
+   --ext-unix-sk                allow external unix sockets
+   --shell-job                  allow shell jobs
+   --page-server                ADDRESS:PORT of the page server
+   --file-locks                 handle file locks, for safety
+   --manage-cgroups-mode        cgroups mode: 'soft' (default), 'full' and 'strict'.

vendor/github.com/opencontainers/runc/man/runc-delete.8.md

@@ -0,0 +1,14 @@
+# NAME
+   runc delete - delete any resources held by the container often used with detached containers
+
+# SYNOPSIS
+   runc delete <container-id>
+
+Where "<container-id>" is the name for the instance of the container.
+
+# EXAMPLE
+For example, if the container id is "ubuntu01" and runc list currently shows the
+status of "ubuntu01" as "destroyed" the following will delete resources held for
+"ubuntu01" removing "ubuntu01" from the runc list of containers:  
+
+       # runc delete ubuntu01

vendor/github.com/opencontainers/runc/man/runc-events.8.md

@@ -0,0 +1,16 @@
+# NAME
+   runc events - display container events such as OOM notifications, cpu, memory, IO and network stats
+
+# SYNOPSIS
+   runc events [command options] <container-id>
+
+Where "<container-id>" is the name for the instance of the container.
+
+# DESCRIPTION
+   The events command displays information about the container. By default the
+information is displayed once every 5 seconds.
+
+# OPTIONS
+   --interval "5s"      set the stats collection interval
+   --stats              display the container's stats then exit
+   

vendor/github.com/opencontainers/runc/man/runc-exec.8.md

@@ -0,0 +1,28 @@
+# NAME
+   runc exec - execute new process inside the container
+
+# SYNOPSIS
+   runc exec [command options] <container-id> <container command>
+
+Where "<container-id>" is the name for the instance of the container and
+"<container command>" is the command to be executed in the container.
+
+# EXAMPLE
+For example, if the container is configured to run the linux ps command the
+following will output a list of processes running in the container:
+
+       # runc exec <container-id> ps
+
+# OPTIONS
+   --console                                    specify the pty slave path for use with the container
+   --cwd                                        current working directory in the container
+   --env, -e [--env option --env option]        set environment variables
+   --tty, -t                                    allocate a pseudo-TTY
+   --user, -u                                   UID (format: <uid>[:<gid>])
+   --process, -p                                path to the process.json
+   --detach, -d                                 detach from the container's process
+   --pid-file                                   specify the file to write the process id to
+   --process-label                              set the asm process label for the process commonly used with selinux
+   --apparmor                                   set the apparmor profile for the process
+   --no-new-privs                               set the no new privileges value for the process
+   --cap, -c [--cap option --cap option]        add a capability to the bounding set for the process

vendor/github.com/opencontainers/runc/man/runc-kill.8.md

@@ -0,0 +1,15 @@
+# NAME
+   runc kill - kill sends the specified signal (default: SIGTERM) to the container's init process
+
+# SYNOPSIS
+   runc kill <container-id> <signal>
+
+Where "<container-id>" is the name for the instance of the container and
+"<signal>" is the signal to be sent to the init process.
+
+# EXAMPLE
+
+For example, if the container id is "ubuntu01" the following will send a "KILL"
+signal to the init process of the "ubuntu01" container:
+
+       # runc kill ubuntu01 KILL

vendor/github.com/opencontainers/runc/man/runc-list.8.md

@@ -0,0 +1,14 @@
+# NAME
+   runc list - lists containers started by runc with the given root
+
+# SYNOPSIS
+   runc list [command options] [arguments...]
+
+# DESCRIPTION
+   The default format is table.  The following will output the list of containers
+in json format:
+
+    # runc list -f json
+
+# OPTIONS
+   --format, -f         select one of: table or json.

vendor/github.com/opencontainers/runc/man/runc-pause.8.md

@@ -0,0 +1,12 @@
+# NAME
+   runc pause - pause suspends all processes inside the container
+
+# SYNOPSIS
+   runc pause <container-id>
+
+Where "<container-id>" is the name for the instance of the container to be
+paused. 
+
+# DESCRIPTION
+   The pause command suspends all processes in the instance of the container.
+Use runc list to identiy instances of containers and their current status.

vendor/github.com/opencontainers/runc/man/runc-restore.8.md

@@ -0,0 +1,24 @@
+# NAME
+   runc restore - restore a container from a previous checkpoint
+
+# SYNOPSIS
+   runc restore [command options] <container-id>
+
+Where "<container-id>" is the name for the instance of the container to be
+restored.
+
+# DESCRIPTION
+   Restores the saved state of the container instance that was previously saved
+using the runc checkpoint command.
+
+# OPTIONS
+   --image-path                 path to criu image files for restoring
+   --work-path                  path for saving work files and logs
+   --tcp-established            allow open tcp connections
+   --ext-unix-sk                allow external unix sockets
+   --shell-job                  allow shell jobs
+   --file-locks                 handle file locks, for safety
+   --manage-cgroups-mode        cgroups mode: 'soft' (default), 'full' and 'strict'.
+   --bundle, -b                 path to the root of the bundle directory
+   --detach, -d                 detach from the container's process
+   --pid-file                   specify the file to write the process id to

vendor/github.com/opencontainers/runc/man/runc-resume.8.md

@@ -0,0 +1,12 @@
+# NAME
+   runc resume - resumes all processes that have been previously paused
+
+# SYNOPSIS
+   runc resume <container-id>
+
+Where "<container-id>" is the name for the instance of the container to be
+resumed.
+
+# DESCRIPTION
+   The resume command resumes all processes in the instance of the container.
+Use runc list to identiy instances of containers and their current status.

vendor/github.com/opencontainers/runc/man/runc-spec.8.md

@@ -0,0 +1,44 @@
+# NAME
+   runc spec - create a new specification file
+
+# SYNOPSIS
+   runc spec [command options] [arguments...]
+
+# DESCRIPTION
+   The spec command creates the new specification file named "config.json" for
+the bundle.
+
+The spec generated is just a starter file. Editing of the spec is required to
+achieve desired results. For example, the newly generated spec includes an args
+parameter that is initially set to call the "sh" command when the container is
+started. Calling "sh" may work for an ubuntu container or busybox, but will not
+work for containers that do not include the "sh" program.
+
+EXAMPLE:
+  To run docker's hello-world container one needs to set the args parameter
+in the spec to call hello. This can be done using the sed command or a text
+editor. The following commands create a bundle for hello-world, change the
+default args parameter in the spec from "sh" to "/hello", then run the hello
+command in a new hello-world container named container1:
+
+    mkdir hello
+    cd hello
+    docker pull hello-world
+    docker export $(docker create hello-world) > hello-world.tar
+    mkdir rootfs
+    tar -C rootfs -xf hello-world.tar
+    runc spec
+    sed -i 's;"sh";"/hello";' config.json
+    runc start container1
+
+In the start command above, "container1" is the name for the instance of the
+container that you are starting. The name you provide for the container instance
+must be unique on your host.
+
+When starting a container through runc, runc needs root privilege. If not
+already running as root, you can use sudo to give runc root privilege. For
+example: "sudo runc start container1" will give runc root privilege to start the
+container on your host.
+
+# OPTIONS
+   --bundle, -b         path to the root of the bundle directory

vendor/github.com/opencontainers/runc/man/runc-start.8.md

@@ -0,0 +1,25 @@
+# NAME
+   runc start - create and run a container
+
+# SYNOPSIS
+   runc start [command options] <container-id>
+
+Where "<container-id>" is your name for the instance of the container that you
+are starting. The name you provide for the container instance must be unique on
+your host.
+
+# DESCRIPTION
+   The start command creates an instance of a container for a bundle. The bundle
+is a directory with a specification file named "config.json" and a root
+filesystem.
+
+The specification file includes an args parameter. The args parameter is used
+to specify command(s) that get run when the container is started. To change the
+command(s) that get executed on start, edit the args parameter of the spec. See
+"runc spec --help" for more explanation.
+
+# OPTIONS
+   --bundle, -b         path to the root of the bundle directory, defaults to the current directory
+   --console            specify the pty slave path for use with the container
+   --detach, -d         detach from the container's process
+   --pid-file           specify the file to write the process id to

vendor/github.com/opencontainers/runc/man/runc-state.8.md

@@ -0,0 +1,11 @@
+# NAME
+   runc state - output the state of a container
+
+# SYNOPSIS
+   runc state <container-id>
+
+Where "<container-id>" is your name for the instance of the container.
+
+# DESCRIPTION
+   The state command outputs current state information for the
+instance of a container.

vendor/github.com/opencontainers/runc/man/runc.8.md

@@ -0,0 +1,53 @@
+# NAME
+   runc - Open Container Initiative runtime
+
+# SYNOPSIS
+   runc [global options] command [command options] [arguments...]
+   
+# DESCRIPTION
+runc is a command line client for running applications packaged according to
+the Open Container Format (OCF) and is a compliant implementation of the
+Open Container Initiative specification.
+
+runc integrates well with existing process supervisors to provide a production
+container runtime environment for applications. It can be used with your
+existing process monitoring tools and the container will be spawned as a
+direct child of the process supervisor.
+
+Containers are configured using bundles. A bundle for a container is a directory
+that includes a specification file named "config.json" and a root filesystem.
+The root filesystem contains the contents of the container. 
+
+To start a new instance of a container:
+
+    # runc start [ -b bundle ] <container-id>
+
+Where "<container-id>" is your name for the instance of the container that you
+are starting. The name you provide for the container instance must be unique on
+your host. Providing the bundle directory using "-b" is optional. The default
+value for "bundle" is the current directory.
+
+# COMMANDS
+   checkpoint   checkpoint a running container
+   delete       delete any resources held by the container often used with detached containers
+   events       display container events such as OOM notifications, cpu, memory, IO and network stats
+   exec         execute new process inside the container
+   kill         kill sends the specified signal (default: SIGTERM) to the container's init process
+   list         lists containers started by runc with the given root
+   pause        pause suspends all processes inside the container
+   restore      restore a container from a previous checkpoint
+   resume       resumes all processes that have been previously paused
+   spec         create a new specification file
+   start        create and run a container
+   state        output the state of a container
+   help, h      Shows a list of commands or help for one command
+   
+# GLOBAL OPTIONS
+   --debug                                      enable debug output for logging
+   --log                                        set the log file path where internal debug information is written
+   --log-format "text"                          set the format used by logs ('text' (default), or 'json')
+   --root "/run/opencontainer/containers"       root directory for storage of container state (this should be located in tmpfs)
+   --criu "criu"                                path to the criu binary used for checkpoint and restore
+   --systemd-cgroup                             enable systemd cgroup support, expects cgroupsPath to be of form "slice:prefix:name" for e.g. "system.slice:runc:434234"
+   --help, -h                                   show help
+   --version, -v                                print the version