Add build-containerd.sh to build containerd from existing repo

Signed-off-by: Lantao Liu <lantaol@google.com>

hack/install/install-deps.sh

@@ -0,0 +1,50 @@
+#!/bin/bash
+
+# Copyright 2017 The Kubernetes Authors.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# 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.
+
+# Dependencies:
+# runc:
+# - libseccomp-dev(Ubuntu,Debian)/libseccomp-devel(Fedora, CentOS, RHEL). Note that
+# libseccomp in ubuntu <=trusty and debian <=jessie is not new enough, backport
+# is required.
+# - libapparmor-dev(Ubuntu,Debian)/libapparmor-devel(Fedora, CentOS, RHEL)
+# containerd:
+# - btrfs-tools(Ubuntu,Debian)/btrfs-progs-devel(Fedora, CentOS, RHEL)
+
+set -o errexit
+set -o nounset
+set -o pipefail
+
+cd $(dirname "${BASH_SOURCE[0]}")
+
+# INSTALL_CNI indicates whether to install CNI. CNI installation
+# makes sense for local testing, but doesn't make sense for cluster
+# setup, because CNI daemonset is usually used to deploy CNI binaries
+# and configurations in cluster.
+INSTALL_CNI=${INSTALL_CNI:-true}
+
+# Install runc
+./install-runc.sh
+
+# Install cni
+if ${INSTALL_CNI}; then
+  ./install-cni.sh
+fi
+
+# Install containerd
+./install-containerd.sh
+
+#Install crictl
+./install-crictl.sh