From 6c6a89f5fa4f48ed2c72c449a9f14de3d78d81e5 Mon Sep 17 00:00:00 2001
From: Rolf Neugebauer <rolf.neugebauer@docker.com>
Date: Mon, 7 Aug 2017 20:36:25 +0100
Subject: [PATCH] docs: Clarify restrictions for packages builds/signing

Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
---
 docs/packages.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/packages.md b/docs/packages.md
index 15bb41675..df6d2625d 100644
--- a/docs/packages.md
+++ b/docs/packages.md
@@ -46,6 +46,11 @@ To build a package on an architecture:
 DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE="<passphrase>" make
 ```
 
+**Note:** You *must* be logged into hub (`docker login`) and the
+passphrase for the key *must* be supplied as an environment
+variable. The build process has to resort to using `expect` to drive
+`notary` so none of the credentials can be entered interactively.
+
 This will:
 - Build a local images as `linuxkit/<image>:<hash>-<arch>`
 - Push it to hub