diff options
| author | Olaf Hering <olaf@aepfle.de> | 2021-07-08 16:56:28 +0200 |
|---|---|---|
| committer | Andrew Cooper <andrew.cooper3@citrix.com> | 2021-07-09 13:28:52 +0100 |
| commit | cf4aa8dfb201a7db3e9ec2d4a2ff56961c7719fb (patch) | |
| tree | 8ea9a0f30c7fe762ce6746f5e7ad32a24b8844f3 | |
| parent | 4905c2da20e2d95ff577033b0513d4bb57a9c086 (diff) | |
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@aepfle.de>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
| -rw-r--r-- | automation/build/README.md | 12 |
1 files changed, 12 insertions, 0 deletions
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 |