| Message ID | 20190803144417.60947-1-cardoe@cardoe.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | automation: add info about container pushes | expand |
On 03/08/2019 15:44, Doug Goldstein wrote: > 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@cardoe.com> Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
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
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@cardoe.com> --- automation/build/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)