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>
This commit is contained in:
Olaf Hering authored and Andrew Cooper committed 2021-07-09 13:28:52 +01:00
1 parent 4905c2da20
commit cf4aa8dfb2
1 file changed
+12
+12
View File
@@ -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
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.