[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [PATCH v1] 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 <olaf@xxxxxxxxx> --- automation/build/README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) I did not actually run the "PUSH" command. diff --git a/automation/build/README.md b/automation/build/README.md index e1fb3124de..7f33ea077b 100644 --- a/automation/build/README.md +++ b/automation/build/README.md @@ -91,5 +91,18 @@ 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 +docker image ls +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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |