[Xen-changelog] [xen staging] automation: add info about container pushes

[patchbot@xxxxxxx]

commit c7a99eee3d7c02e1d4dc8856a810769f64479325
Author:     Doug Goldstein <cardoe@xxxxxxxxxx>
AuthorDate: Sat Aug 3 09:44:17 2019 -0500
Commit:     Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
CommitDate: Sat Aug 3 15:55:39 2019 +0100

    automation: add info about container pushes
    
    To be able to push a container, users must have access and have logged
    into the container registry. The docs did not explain this fully so this
    documents the steps better.
    
    Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx>
    Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
---
 automation/build/README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/automation/build/README.md b/automation/build/README.md
index d8c8a18e33..476f82cf45 100644
--- a/automation/build/README.md
+++ b/automation/build/README.md
@@ -66,6 +66,10 @@ There is a makefile to make this process easier. You should 
be
 able to run `make DISTRO/VERSION` to have Docker build the container
 for you. If you define the `PUSH` environment variable when running the
 former `make` command, it will push the container to the [registry] if
-you have access to do so.
+you have access to do so and have your Docker logged into the registry.
+
+To login you must run `docker login registry.gitlab.com`. For more
+information see the [registry help].
 
 [registry]: https://gitlab.com/xen-project/xen/container_registry
+[registry help]: https://gitlab.com/help/user/project/container_registry
--
generated by git-patchbot for /home/xen/git/xen.git#staging

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/xen-changelog