Skip to contentSkip to conversation

automation: document how to refresh a container

PATCH In review Olaf Hering 2 participants 4 messages Jul 8, 2021 – Jul 9, 2021

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 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.

---
 automation/build/README.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

I did not actually run the "PUSH" command.

automation/build/README.md +13 -0
index e1fb3124de..7f33ea077b 100644
@@ -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
#1 lore raw
Quoted 16 lines · Olaf Hering

The Tumbleweed container should be updated often. Describe the neccessary steps how to refresh and test it before pushing the new image to gitlab.

---
 automation/build/README.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

I did not actually run the "PUSH" command.

automation/build/README.md +0 -0
index e1fb3124de..7f33ea077b 100644

automation/build/README.md you have access to do so and have your Docker logged into the registry. · line 100

Quoted 10 lines
automation/build/README.md +7 -0
@@ -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

Do we need the ls here?  That sounds a little like debugging.

Otherwise, LGTM.

Quoted 9 lines
automation/build/README.md +6 -0
+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 lore raw

Am Fri, 9 Jul 2021 13:02:54 +0100
schrieb Andrew Cooper <[email protected]>:

Quoted 1 line

Do we need the ls here?  That sounds a little like debugging.

Maybe not, it may show a long list of unrelated stuff.
It is just to verify a fresh container exists, as you said, just for debugging.

Olaf

#3 lore raw
Quoted 6 lines · Olaf Hering

Am Fri, 9 Jul 2021 13:02:54 +0100
schrieb Andrew Cooper <[email protected]>:

Quoted 1 line

Do we need the ls here?  That sounds a little like debugging.

Maybe not, it may show a long list of unrelated stuff.
It is just to verify a fresh container exists, as you said, just for debugging.

Ok - I'll drop that line and commit, then we can see about rebuilding the container.

~Andrew