From cf4aa8dfb201a7db3e9ec2d4a2ff56961c7719fb Mon Sep 17 00:00:00 2001 From: Olaf Hering Date: Thu, 8 Jul 2021 16:56:28 +0200 Subject: [PATCH] automation: document how to refresh a container The Tumbleweed container should be updated often. Describe the neccessary steps how to refresh and test it before pushing the new image to gitlab. Signed-off-by: Olaf Hering Acked-by: Andrew Cooper --- automation/build/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/automation/build/README.md b/automation/build/README.md index e1fb3124de..2137957408 100644 --- a/automation/build/README.md +++ b/automation/build/README.md @@ -91,5 +91,17 @@ 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]. +This example shows how to refresh a container for a rolling release +such as openSUSE Tumbleweed. Login with the gitlab.com credentials. + +``` +docker login registry.gitlab.com/xen-project/xen +make -C automation/build suse/opensuse-tumbleweed +env CONTAINER_NO_PULL=1 \ + CONTAINER=tumbleweed \ + automation/scripts/containerize bash -exc './configure && make' +make -C automation/build suse/opensuse-tumbleweed PUSH=1 +``` + [registry]: https://gitlab.com/xen-project/xen/container_registry [registry help]: https://gitlab.com/help/user/project/container_registry -- 2.30.2