@@ -1,4 +1,4 @@

-# Generate AUTHORS: project/generate-authors.sh

+# Generate AUTHORS: hack/generate-authors.sh

 # Tip for finding duplicates (besides scanning the output of AUTHORS for name

 # duplicates that aren't also email duplicates): scan the output of:

@@ -1,5 +1,5 @@

 # This file lists all individuals having contributed content to the repository.

-# For how it is generated, see `project/generate-authors.sh`.

+# For how it is generated, see `hack/generate-authors.sh`.

 Aanand Prasad <aanand.prasad@gmail.com>

 Aaron Feng <aaron.feng@gmail.com>

new file mode 100755

@@ -0,0 +1,22 @@

+#!/usr/bin/env bash

+

+## Run this script from the root of the docker repository

+## to query project stats useful to the maintainers.

+## You will need to install `pulls` and `issues` from

+## http://github.com/crosbymichael/pulls

+

+set -e

+

+echo -n "Open pulls: "

+PULLS=$(pulls | wc -l); let PULLS=$PULLS-1

+echo $PULLS

+

+echo -n "Pulls alru: "

+pulls alru

+

+echo -n "Open issues: "

+ISSUES=$(issues list | wc -l); let ISSUES=$ISSUES-1

+echo $ISSUES

+

+echo -n "Issues alru: "

+issues alru

new file mode 100644

@@ -0,0 +1,105 @@

+#!/bin/sh

+

+# This is a convenience script for reporting issues that include a base

+# template of information. See https://github.com/docker/docker/pull/8845

+

+set -e

+

+DOCKER_ISSUE_URL=${DOCKER_ISSUE_URL:-"https://github.com/docker/docker/issues/new"}

+DOCKER_ISSUE_NAME_PREFIX=${DOCKER_ISSUE_NAME_PREFIX:-"Report: "}

+DOCKER=${DOCKER:-"docker"}

+DOCKER_COMMAND="${DOCKER}"

+export DOCKER_COMMAND

+

+# pulled from https://gist.github.com/cdown/1163649

+function urlencode() {

+	# urlencode <string>

+

+	local length="${#1}"

+	for (( i = 0; i < length; i++ )); do

+			local c="${1:i:1}"

+			case $c in

+					[a-zA-Z0-9.~_-]) printf "$c" ;;

+					*) printf '%%%02X' "'$c"

+			esac

+	done

+}

+

+function template() {

+# this should always match the template from CONTRIBUTING.md

+	cat <<- EOM

+	Description of problem:

+	

+	

+	\`docker version\`:

+	`${DOCKER_COMMAND} -D version`

+	

+	

+	\`docker info\`:

+	`${DOCKER_COMMAND} -D info`

+	

+	

+	\`uname -a\`:

+	`uname -a`

+	

+	

+	Environment details (AWS, VirtualBox, physical, etc.):

+	

+	

+	How reproducible:

+	

+	

+	Steps to Reproduce:

+	1.

+	2.

+	3.

+	

+	

+	Actual Results:

+	

+	

+	Expected Results:

+	

+	

+	Additional info:

+	

+	

+	EOM

+}

+

+function format_issue_url() {

+	if [ ${#@} -ne 2 ] ; then

+		return 1

+	fi

+	local issue_name=$(urlencode "${DOCKER_ISSUE_NAME_PREFIX}${1}")

+	local issue_body=$(urlencode "${2}")

+	echo "${DOCKER_ISSUE_URL}?title=${issue_name}&body=${issue_body}"

+}

+

+

+echo -ne "Do you use \`sudo\` to call docker? [y|N]: "

+read -r -n 1 use_sudo

+echo ""

+

+if [ "x${use_sudo}" = "xy" -o "x${use_sudo}" = "xY" ]; then 

+	export DOCKER_COMMAND="sudo ${DOCKER}"

+fi

+

+echo -ne "Title of new issue?: "

+read -r issue_title

+echo ""

+

+issue_url=$(format_issue_url "${issue_title}" "$(template)")

+

+if which xdg-open 2>/dev/null >/dev/null ; then

+	echo -ne "Would like to launch this report in your browser? [Y|n]: "

+	read -r -n 1 launch_now

+	echo ""

+

+	if [ "${launch_now}" != "n" -a "${launch_now}" != "N" ]; then

+		xdg-open "${issue_url}"

+	fi

+fi

+

+echo "If you would like to manually open the url, you can open this link if your browser: ${issue_url}"

+

@@ -242,9 +242,9 @@ build and run a `docker` binary in your container.

 4. From the `/go/src/github.com/docker/docker` directory make a `docker` binary with the `make.sh` script.

-        root@5f8630b873fe:/go/src/github.com/docker/docker# project/make.sh binary

+        root@5f8630b873fe:/go/src/github.com/docker/docker# hack/make.sh binary

-    You only call `project/make.sh` to build a binary _inside_ a Docker

+    You only call `hack/make.sh` to build a binary _inside_ a Docker

     development container as you are now. On your host, you'll use `make`

     commands (more about this later). 

@@ -133,7 +133,7 @@ Run the entire test suite on your current repository:

 ### Run test targets inside the development container

 If you are working inside a Docker development container, you use the

-`project/make.sh` script to run tests. The `project/make.sh` script doesn't

+`hack/make.sh` script to run tests. The `hack/make.sh` script doesn't

 have a single target that runs all the tests. Instead, you provide a single

 commmand line with multiple targets that does the same thing.

@@ -148,9 +148,9 @@ Try this now.

         $ docker run --privileged --rm -ti -v `pwd`:/go/src/github.com/docker/docker dry-run-test /bin/bash

-3. Run the tests using the `project/make.sh` script.

+3. Run the tests using the `hack/make.sh` script.

-        root@5f8630b873fe:/go/src/github.com/docker/docker# project/make.sh dynbinary binary cross test-unit test-integration test-integration-cli test-docker-py

+        root@5f8630b873fe:/go/src/github.com/docker/docker# hack/make.sh dynbinary binary cross test-unit test-integration test-integration-cli test-docker-py

     The tests run just as they did within your local host.

@@ -158,7 +158,7 @@ Try this now.

 Of course, you can also run a subset of these targets too. For example, to run

 just the unit tests:

-    root@5f8630b873fe:/go/src/github.com/docker/docker# project/make.sh dynbinary binary cross test-unit

+    root@5f8630b873fe:/go/src/github.com/docker/docker# hack/make.sh dynbinary binary cross test-unit

 Most test targets require that you build these precursor targets first:

 `dynbinary binary cross`

@@ -174,7 +174,7 @@ your local host you can run the `TestBuild` test with this command:

 To run the same test inside your Docker development container, you do this:

-        root@5f8630b873fe:/go/src/github.com/docker/docker# TESTFLAGS='-run ^TestBuild$' project/make.sh

+        root@5f8630b873fe:/go/src/github.com/docker/docker# TESTFLAGS='-run ^TestBuild$' hack/make.sh

 ## If test under Boot2Docker fail do to space errors

deleted file mode 120000

@@ -1 +0,0 @@

-project

\ No newline at end of file

new file mode 100755

@@ -0,0 +1,88 @@

+#!/bin/bash

+set -e

+

+# DinD: a wrapper script which allows docker to be run inside a docker container.

+# Original version by Jerome Petazzoni <jerome@docker.com>

+# See the blog post: http://blog.docker.com/2013/09/docker-can-now-run-within-docker/

+#

+# This script should be executed inside a docker container in privilieged mode

+# ('docker run --privileged', introduced in docker 0.6).

+

+# Usage: dind CMD [ARG...]

+

+# apparmor sucks and Docker needs to know that it's in a container (c) @tianon

+export container=docker

+

+# First, make sure that cgroups are mounted correctly.

+CGROUP=/cgroup

+

+mkdir -p "$CGROUP"

+

+if ! mountpoint -q "$CGROUP"; then

+	mount -n -t tmpfs -o uid=0,gid=0,mode=0755 cgroup $CGROUP || {

+		echo >&2 'Could not make a tmpfs mount. Did you use --privileged?'

+		exit 1

+	}

+fi

+

+if [ -d /sys/kernel/security ] && ! mountpoint -q /sys/kernel/security; then

+	mount -t securityfs none /sys/kernel/security || {

+		echo >&2 'Could not mount /sys/kernel/security.'

+		echo >&2 'AppArmor detection and -privileged mode might break.'

+	}

+fi

+

+# Mount the cgroup hierarchies exactly as they are in the parent system.

+for SUBSYS in $(cut -d: -f2 /proc/1/cgroup); do

+	mkdir -p "$CGROUP/$SUBSYS"

+	if ! mountpoint -q $CGROUP/$SUBSYS; then

+		mount -n -t cgroup -o "$SUBSYS" cgroup "$CGROUP/$SUBSYS"

+	fi

+

+	# The two following sections address a bug which manifests itself

+	# by a cryptic "lxc-start: no ns_cgroup option specified" when

+	# trying to start containers withina container.

+	# The bug seems to appear when the cgroup hierarchies are not

+	# mounted on the exact same directories in the host, and in the

+	# container.

+

+	# Named, control-less cgroups are mounted with "-o name=foo"

+	# (and appear as such under /proc/<pid>/cgroup) but are usually

+	# mounted on a directory named "foo" (without the "name=" prefix).

+	# Systemd and OpenRC (and possibly others) both create such a

+	# cgroup. To avoid the aforementioned bug, we symlink "foo" to

+	# "name=foo". This shouldn't have any adverse effect.

+	name="${SUBSYS#name=}"

+	if [ "$name" != "$SUBSYS" ]; then

+		ln -s "$SUBSYS" "$CGROUP/$name"

+	fi

+

+	# Likewise, on at least one system, it has been reported that

+	# systemd would mount the CPU and CPU accounting controllers

+	# (respectively "cpu" and "cpuacct") with "-o cpuacct,cpu"

+	# but on a directory called "cpu,cpuacct" (note the inversion

+	# in the order of the groups). This tries to work around it.

+	if [ "$SUBSYS" = 'cpuacct,cpu' ]; then

+		ln -s "$SUBSYS" "$CGROUP/cpu,cpuacct"

+	fi

+done

+

+# Note: as I write those lines, the LXC userland tools cannot setup

+# a "sub-container" properly if the "devices" cgroup is not in its

+# own hierarchy. Let's detect this and issue a warning.

+if ! grep -q :devices: /proc/1/cgroup; then

+	echo >&2 'WARNING: the "devices" cgroup should be in its own hierarchy.'

+fi

+if ! grep -qw devices /proc/1/cgroup; then

+	echo >&2 'WARNING: it looks like the "devices" cgroup is not mounted.'

+fi

+

+# Mount /tmp

+mount -t tmpfs none /tmp

+

+if [ $# -gt 0 ]; then

+	exec "$@"

+fi

+

+echo >&2 'ERROR: No command specified.'

+echo >&2 'You probably want to run hack/make.sh, or maybe a shell?'

new file mode 100755

@@ -0,0 +1,15 @@

+#!/bin/bash

+set -e

+

+cd "$(dirname "$(readlink -f "$BASH_SOURCE")")/.."

+

+# see also ".mailmap" for how email addresses and names are deduplicated

+

+{

+	cat <<-'EOH'

+	# This file lists all individuals having contributed content to the repository.

+	# For how it is generated, see `hack/generate-authors.sh`.

+	EOH

+	echo

+	git log --format='%aN <%aE>' | LC_ALL=C.UTF-8 sort -uf

+} > AUTHORS

new file mode 100755

@@ -0,0 +1,225 @@

+#!/bin/sh

+set -e

+#

+# This script is meant for quick & easy install via:

+#   'curl -sSL https://get.docker.com/ | sh'

+# or:

+#   'wget -qO- https://get.docker.com/ | sh'

+#

+#

+# Docker Maintainers:

+#   To update this script on https://get.docker.com,

+#   use hack/release.sh during a normal release,

+#   or the following one-liner for script hotfixes:

+#     s3cmd put --acl-public -P hack/install.sh s3://get.docker.com/index

+#

+

+url='https://get.docker.com/'

+

+command_exists() {

+	command -v "$@" > /dev/null 2>&1

+}

+

+case "$(uname -m)" in

+	*64)

+		;;

+	*)

+		echo >&2 'Error: you are not using a 64bit platform.'

+		echo >&2 'Docker currently only supports 64bit platforms.'

+		exit 1

+		;;

+esac

+

+if command_exists docker || command_exists lxc-docker; then

+	echo >&2 'Warning: "docker" or "lxc-docker" command appears to already exist.'

+	echo >&2 'Please ensure that you do not already have docker installed.'

+	echo >&2 'You may press Ctrl+C now to abort this process and rectify this situation.'

+	( set -x; sleep 20 )

+fi

+

+user="$(id -un 2>/dev/null || true)"

+

+sh_c='sh -c'

+if [ "$user" != 'root' ]; then

+	if command_exists sudo; then

+		sh_c='sudo -E sh -c'

+	elif command_exists su; then

+		sh_c='su -c'

+	else

+		echo >&2 'Error: this installer needs the ability to run commands as root.'

+		echo >&2 'We are unable to find either "sudo" or "su" available to make this happen.'

+		exit 1

+	fi

+fi

+

+curl=''

+if command_exists curl; then

+	curl='curl -sSL'

+elif command_exists wget; then

+	curl='wget -qO-'

+elif command_exists busybox && busybox --list-modules | grep -q wget; then

+	curl='busybox wget -qO-'

+fi

+

+# perform some very rudimentary platform detection

+lsb_dist=''

+if command_exists lsb_release; then

+	lsb_dist="$(lsb_release -si)"

+fi

+if [ -z "$lsb_dist" ] && [ -r /etc/lsb-release ]; then

+	lsb_dist="$(. /etc/lsb-release && echo "$DISTRIB_ID")"

+fi

+if [ -z "$lsb_dist" ] && [ -r /etc/debian_version ]; then

+	lsb_dist='debian'

+fi

+if [ -z "$lsb_dist" ] && [ -r /etc/fedora-release ]; then

+	lsb_dist='fedora'

+fi

+if [ -z "$lsb_dist" ] && [ -r /etc/os-release ]; then

+	lsb_dist="$(. /etc/os-release && echo "$ID")"

+fi

+

+lsb_dist="$(echo "$lsb_dist" | tr '[:upper:]' '[:lower:]')"

+case "$lsb_dist" in

+	amzn|fedora)

+		if [ "$lsb_dist" = 'amzn' ]; then

+			(

+				set -x

+				$sh_c 'sleep 3; yum -y -q install docker'

+			)

+		else

+			(

+				set -x

+				$sh_c 'sleep 3; yum -y -q install docker-io'

+			)

+		fi

+		if command_exists docker && [ -e /var/run/docker.sock ]; then

+			(

+				set -x

+				$sh_c 'docker version'

+			) || true

+		fi

+		your_user=your-user

+		[ "$user" != 'root' ] && your_user="$user"

+		echo

+		echo 'If you would like to use Docker as a non-root user, you should now consider'

+		echo 'adding your user to the "docker" group with something like:'

+		echo

+		echo '  sudo usermod -aG docker' $your_user

+		echo

+		echo 'Remember that you will have to log out and back in for this to take effect!'

+		echo

+		exit 0

+		;;

+

+	ubuntu|debian|linuxmint)

+		export DEBIAN_FRONTEND=noninteractive

+

+		did_apt_get_update=

+		apt_get_update() {

+			if [ -z "$did_apt_get_update" ]; then

+				( set -x; $sh_c 'sleep 3; apt-get update' )

+				did_apt_get_update=1

+			fi

+		}

+

+		# aufs is preferred over devicemapper; try to ensure the driver is available.

+		if ! grep -q aufs /proc/filesystems && ! $sh_c 'modprobe aufs'; then

+			kern_extras="linux-image-extra-$(uname -r)"

+

+			apt_get_update

+			( set -x; $sh_c 'sleep 3; apt-get install -y -q '"$kern_extras" ) || true

+

+			if ! grep -q aufs /proc/filesystems && ! $sh_c 'modprobe aufs'; then

+				echo >&2 'Warning: tried to install '"$kern_extras"' (for AUFS)'

+				echo >&2 ' but we still have no AUFS.  Docker may not work. Proceeding anyways!'

+				( set -x; sleep 10 )

+			fi

+		fi

+

+		# install apparmor utils if they're missing and apparmor is enabled in the kernel

+		# otherwise Docker will fail to start

+		if [ "$(cat /sys/module/apparmor/parameters/enabled 2>/dev/null)" = 'Y' ]; then

+			if command -v apparmor_parser &> /dev/null; then

+				echo 'apparmor is enabled in the kernel and apparmor utils were already installed'

+			else

+				echo 'apparmor is enabled in the kernel, but apparmor_parser missing'

+				apt_get_update

+				( set -x; $sh_c 'sleep 3; apt-get install -y -q apparmor' )

+			fi

+		fi

+

+		if [ ! -e /usr/lib/apt/methods/https ]; then

+			apt_get_update

+			( set -x; $sh_c 'sleep 3; apt-get install -y -q apt-transport-https ca-certificates' )

+		fi

+		if [ -z "$curl" ]; then

+			apt_get_update

+			( set -x; $sh_c 'sleep 3; apt-get install -y -q curl ca-certificates' )

+			curl='curl -sSL'

+		fi

+		(

+			set -x

+			if [ "https://get.docker.com/" = "$url" ]; then

+				$sh_c "apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 36A1D7869245C8950F966E92D8576A8BA88D21E9"

+			elif [ "https://test.docker.com/" = "$url" ]; then

+				$sh_c "apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 740B314AE3941731B942C66ADF4FD13717AAD7D6"

+			else

+				$sh_c "$curl ${url}gpg | apt-key add -"

+			fi

+			$sh_c "echo deb ${url}ubuntu docker main > /etc/apt/sources.list.d/docker.list"

+			$sh_c 'sleep 3; apt-get update; apt-get install -y -q lxc-docker'

+		)

+		if command_exists docker && [ -e /var/run/docker.sock ]; then

+			(

+				set -x

+				$sh_c 'docker version'

+			) || true

+		fi

+		your_user=your-user

+		[ "$user" != 'root' ] && your_user="$user"

+		echo

+		echo 'If you would like to use Docker as a non-root user, you should now consider'

+		echo 'adding your user to the "docker" group with something like:'

+		echo

+		echo '  sudo usermod -aG docker' $your_user

+		echo

+		echo 'Remember that you will have to log out and back in for this to take effect!'

+		echo

+		exit 0

+		;;

+

+	gentoo)

+		if [ "$url" = "https://test.docker.com/" ]; then

+			echo >&2

+			echo >&2 '  You appear to be trying to install the latest nightly build in Gentoo.'

+			echo >&2 '  The portage tree should contain the latest stable release of Docker, but'

+			echo >&2 '  if you want something more recent, you can always use the live ebuild'

+			echo >&2 '  provided in the "docker" overlay available via layman.  For more'

+			echo >&2 '  instructions, please see the following URL:'

+			echo >&2 '    https://github.com/tianon/docker-overlay#using-this-overlay'

+			echo >&2 '  After adding the "docker" overlay, you should be able to:'

+			echo >&2 '    emerge -av =app-emulation/docker-9999'

+			echo >&2

+			exit 1

+		fi

+

+		(

+			set -x

+			$sh_c 'sleep 3; emerge app-emulation/docker'

+		)

+		exit 0

+		;;

+esac

+

+cat >&2 <<'EOF'

+

+  Either your platform is not easily detectable, is not supported by this

+  installer script (yet - PRs welcome! [hack/install.sh]), or does not yet have

+  a package for Docker.  Please visit the following URL for more detailed

+  installation instructions:

+

+    https://docs.docker.com/en/latest/installation/

+

+EOF

+exit 1

new file mode 100755

@@ -0,0 +1,273 @@

+#!/usr/bin/env bash

+set -e

+

+# This script builds various binary artifacts from a checkout of the docker

+# source code.

+#

+# Requirements:

+# - The current directory should be a checkout of the docker source code

+#   (http://github.com/docker/docker). Whatever version is checked out

+#   will be built.

+# - The VERSION file, at the root of the repository, should exist, and

+#   will be used as Docker binary version and package version.

+# - The hash of the git commit will also be included in the Docker binary,

+#   with the suffix -dirty if the repository isn't clean.

+# - The script is intented to be run inside the docker container specified

+#   in the Dockerfile at the root of the source. In other words:

+#   DO NOT CALL THIS SCRIPT DIRECTLY.

+# - The right way to call this script is to invoke "make" from

+#   your checkout of the Docker repository.

+#   the Makefile will do a "docker build -t docker ." and then

+#   "docker run hack/make.sh" in the resulting image.

+#

+

+set -o pipefail

+

+export DOCKER_PKG='github.com/docker/docker'

+

+# We're a nice, sexy, little shell script, and people might try to run us;

+# but really, they shouldn't. We want to be in a container!

+if [ "$(pwd)" != "/go/src/$DOCKER_PKG" ] || [ -z "$DOCKER_CROSSPLATFORMS" ]; then

+	{

+		echo "# WARNING! I don't seem to be running in the Docker container."

+		echo "# The result of this command might be an incorrect build, and will not be"

+		echo "#   officially supported."

+		echo "#"

+		echo "# Try this instead: make all"

+		echo "#"

+	} >&2

+fi

+

+echo

+

+# List of bundles to create when no argument is passed

+DEFAULT_BUNDLES=(

+	validate-dco

+	validate-gofmt

+	validate-toml

+

+	binary

+

+	test-unit

+	test-integration-cli

+	test-docker-py

+

+	dynbinary

+	test-integration

+

+	cover

+	cross

+	tgz

+	ubuntu

+)

+

+VERSION=$(cat ./VERSION)

+if command -v git &> /dev/null && git rev-parse &> /dev/null; then

+	GITCOMMIT=$(git rev-parse --short HEAD)

+	if [ -n "$(git status --porcelain --untracked-files=no)" ]; then

+		GITCOMMIT="$GITCOMMIT-dirty"

+	fi

+elif [ "$DOCKER_GITCOMMIT" ]; then

+	GITCOMMIT="$DOCKER_GITCOMMIT"

+else

+	echo >&2 'error: .git directory missing and DOCKER_GITCOMMIT not specified'

+	echo >&2 '  Please either build with the .git directory accessible, or specify the'

+	echo >&2 '  exact (--short) commit hash you are building using DOCKER_GITCOMMIT for'

+	echo >&2 '  future accountability in diagnosing build issues.  Thanks!'

+	exit 1

+fi

+

+if [ "$AUTO_GOPATH" ]; then

+	rm -rf .gopath

+	mkdir -p .gopath/src/"$(dirname "${DOCKER_PKG}")"

+	ln -sf ../../../.. .gopath/src/"${DOCKER_PKG}"

+	export GOPATH="$(pwd)/.gopath:$(pwd)/vendor"

+fi

+

+if [ ! "$GOPATH" ]; then

+	echo >&2 'error: missing GOPATH; please see http://golang.org/doc/code.html#GOPATH'

+	echo >&2 '  alternatively, set AUTO_GOPATH=1'

+	exit 1

+fi

+

+if [ -z "$DOCKER_CLIENTONLY" ]; then

+	DOCKER_BUILDTAGS+=" daemon"

+fi

+

+if [ "$DOCKER_EXECDRIVER" = 'lxc' ]; then

+	DOCKER_BUILDTAGS+=' test_no_exec'

+fi

+

+# Use these flags when compiling the tests and final binary

+

+IAMSTATIC='true'

+source "$(dirname "$BASH_SOURCE")/make/.go-autogen"

+LDFLAGS='-w'

+

+LDFLAGS_STATIC='-linkmode external'

+# Cgo -H windows is incompatible with -linkmode external.

+if [ "$(go env GOOS)" == 'windows' ]; then

+	LDFLAGS_STATIC=''

+fi

+EXTLDFLAGS_STATIC='-static'

+# ORIG_BUILDFLAGS is necessary for the cross target which cannot always build

+# with options like -race.

+ORIG_BUILDFLAGS=( -a -tags "netgo static_build $DOCKER_BUILDTAGS" -installsuffix netgo )

+# see https://github.com/golang/go/issues/9369#issuecomment-69864440 for why -installsuffix is necessary here

+BUILDFLAGS=( $BUILDFLAGS "${ORIG_BUILDFLAGS[@]}" )

+# Test timeout.

+: ${TIMEOUT:=30m}

+TESTFLAGS+=" -test.timeout=${TIMEOUT}"

+

+# A few more flags that are specific just to building a completely-static binary (see hack/make/binary)

+# PLEASE do not use these anywhere else.

+EXTLDFLAGS_STATIC_DOCKER="$EXTLDFLAGS_STATIC -lpthread -Wl,--unresolved-symbols=ignore-in-object-files"

+LDFLAGS_STATIC_DOCKER="

+	$LDFLAGS_STATIC

+	-extldflags \"$EXTLDFLAGS_STATIC_DOCKER\"

+"

+

+if [ "$(uname -s)" = 'FreeBSD' ]; then

+	# Tell cgo the compiler is Clang, not GCC

+	# https://code.google.com/p/go/source/browse/src/cmd/cgo/gcc.go?spec=svne77e74371f2340ee08622ce602e9f7b15f29d8d3&r=e6794866ebeba2bf8818b9261b54e2eef1c9e588#752

+	export CC=clang

+

+	# "-extld clang" is a workaround for

+	# https://code.google.com/p/go/issues/detail?id=6845

+	LDFLAGS="$LDFLAGS -extld clang"

+fi

+

+# If sqlite3.h doesn't exist under /usr/include,

+# check /usr/local/include also just in case

+# (e.g. FreeBSD Ports installs it under the directory)

+if [ ! -e /usr/include/sqlite3.h ] && [ -e /usr/local/include/sqlite3.h ]; then

+	export CGO_CFLAGS='-I/usr/local/include'

+	export CGO_LDFLAGS='-L/usr/local/lib'

+fi

+

+HAVE_GO_TEST_COVER=

+if \

+	go help testflag | grep -- -cover > /dev/null \

+	&& go tool -n cover > /dev/null 2>&1 \

+; then

+	HAVE_GO_TEST_COVER=1

+fi

+

+# If $TESTFLAGS is set in the environment, it is passed as extra arguments to 'go test'.

+# You can use this to select certain tests to run, eg.

+#

+#   TESTFLAGS='-run ^TestBuild$' ./hack/make.sh test

+#

+go_test_dir() {

+	dir=$1

+	coverpkg=$2

+	testcover=()

+	if [ "$HAVE_GO_TEST_COVER" ]; then

+		# if our current go install has -cover, we want to use it :)

+		mkdir -p "$DEST/coverprofiles"

+		coverprofile="docker${dir#.}"

+		coverprofile="$DEST/coverprofiles/${coverprofile//\//-}"

+		testcover=( -cover -coverprofile "$coverprofile" $coverpkg )

+	fi

+	(

+		export DEST

+		echo '+ go test' $TESTFLAGS "${DOCKER_PKG}${dir#.}"

+		cd "$dir"

+		test_env go test ${testcover[@]} -ldflags "$LDFLAGS" "${BUILDFLAGS[@]}" $TESTFLAGS

+	)

+}

+test_env() {

+	# use "env -i" to tightly control the environment variables that bleed into the tests

+	env -i \

+		DEST="$DEST" \

+		DOCKER_EXECDRIVER="$DOCKER_EXECDRIVER" \

+		DOCKER_GRAPHDRIVER="$DOCKER_GRAPHDRIVER" \

+		DOCKER_HOST="$DOCKER_HOST" \

+		GOPATH="$GOPATH" \

+		HOME="$DEST/fake-HOME" \

+		PATH="$PATH" \

+		TEST_DOCKERINIT_PATH="$TEST_DOCKERINIT_PATH" \

+		"$@"

+}

+

+# a helper to provide ".exe" when it's appropriate

+binary_extension() {

+	if [ "$(go env GOOS)" = 'windows' ]; then

+		echo -n '.exe'

+	fi

+}

+

+# This helper function walks the current directory looking for directories

+# holding certain files ($1 parameter), and prints their paths on standard

+# output, one per line.

+find_dirs() {

+	find . -not \( \

+		\( \

+			-path './vendor/*' \

+			-o -path './integration/*' \

+			-o -path './integration-cli/*' \

+			-o -path './contrib/*' \

+			-o -path './pkg/mflag/example/*' \

+			-o -path './.git/*' \

+			-o -path './bundles/*' \

+			-o -path './docs/*' \

+			-o -path './pkg/libcontainer/nsinit/*' \

+		\) \

+		-prune \

+	\) -name "$1" -print0 | xargs -0n1 dirname | sort -u

+}

+

+hash_files() {

+	while [ $# -gt 0 ]; do

+		f="$1"

+		shift

+		dir="$(dirname "$f")"

+		base="$(basename "$f")"

+		for hashAlgo in md5 sha256; do

+			if command -v "${hashAlgo}sum" &> /dev/null; then

+				(

+					# subshell and cd so that we get output files like:

+					#   $HASH docker-$VERSION

+					# instead of:

+					#   $HASH /go/src/github.com/.../$VERSION/binary/docker-$VERSION

+					cd "$dir"

+					"${hashAlgo}sum" "$base" > "$base.$hashAlgo"

+				)

+			fi

+		done

+	done

+}

+

+bundle() {

+	bundlescript=$1

+	bundle=$(basename $bundlescript)

+	echo "---> Making bundle: $bundle (in bundles/$VERSION/$bundle)"

+	mkdir -p bundles/$VERSION/$bundle

+	source "$bundlescript" "$(pwd)/bundles/$VERSION/$bundle"

+}

+

+main() {

+	# We want this to fail if the bundles already exist and cannot be removed.

+	# This is to avoid mixing bundles from different versions of the code.

+	mkdir -p bundles

+	if [ -e "bundles/$VERSION" ]; then

+		echo "bundles/$VERSION already exists. Removing."

+		rm -fr bundles/$VERSION && mkdir bundles/$VERSION || exit 1

+		echo

+	fi

+	SCRIPTDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

+	if [ $# -lt 1 ]; then

+		bundles=(${DEFAULT_BUNDLES[@]})

+	else

+		bundles=($@)

+	fi

+	for bundle in ${bundles[@]}; do

+		bundle $SCRIPTDIR/make/$bundle

+		echo

+	done

+

+	# if we get all the way through successfully, let's delete our autogenerated code!

+	rm -r autogen

+}

+

+main "$@"

new file mode 100644

@@ -0,0 +1,32 @@

+#!/bin/bash

+set -e

+

+IAMSTATIC="true"

+source "$(dirname "$BASH_SOURCE")/.go-autogen"

+

+# dockerinit still needs to be a static binary, even if docker is dynamic

+go build \

+	-o "$DEST/dockerinit-$VERSION" \

+	"${BUILDFLAGS[@]}" \

+	-ldflags "

+		$LDFLAGS

+		$LDFLAGS_STATIC

+		-extldflags \"$EXTLDFLAGS_STATIC\"

+	" \

+	./dockerinit

+echo "Created binary: $DEST/dockerinit-$VERSION"

+ln -sf "dockerinit-$VERSION" "$DEST/dockerinit"

+

+sha1sum=

+if command -v sha1sum &> /dev/null; then

+	sha1sum=sha1sum

+elif command -v shasum &> /dev/null; then

+	# Mac OS X - why couldn't they just use the same command name and be happy?

+	sha1sum=shasum

+else

+	echo >&2 'error: cannot find sha1sum command or equivalent'

+	exit 1

+fi

+

+# sha1 our new dockerinit to ensure separate docker and dockerinit always run in a perfect pair compiled for one another

+export DOCKER_INITSHA1="$($sha1sum $DEST/dockerinit-$VERSION | cut -d' ' -f1)"