* [PATCH v1] automation: document how to refresh a container
@ 2021-07-08 14:56 Olaf Hering
2021-07-09 12:02 ` Andrew Cooper
0 siblings, 1 reply; 4+ messages in thread
From: Olaf Hering @ 2021-07-08 14:56 UTC (permalink / raw)
To: xen-devel; +Cc: Olaf Hering, Doug Goldstein
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>
---
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
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v1] automation: document how to refresh a container
2021-07-08 14:56 [PATCH v1] automation: document how to refresh a container Olaf Hering
@ 2021-07-09 12:02 ` Andrew Cooper
2021-07-09 12:23 ` Olaf Hering
0 siblings, 1 reply; 4+ messages in thread
From: Andrew Cooper @ 2021-07-09 12:02 UTC (permalink / raw)
To: Olaf Hering, xen-devel; +Cc: Doug Goldstein
On 08/07/2021 15:56, Olaf Hering wrote:
> 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>
> ---
> 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
Do we need the ls here? That sounds a little like debugging.
Otherwise, LGTM.
> +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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v1] automation: document how to refresh a container
2021-07-09 12:02 ` Andrew Cooper
@ 2021-07-09 12:23 ` Olaf Hering
2021-07-09 12:28 ` Andrew Cooper
0 siblings, 1 reply; 4+ messages in thread
From: Olaf Hering @ 2021-07-09 12:23 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Doug Goldstein
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
Am Fri, 9 Jul 2021 13:02:54 +0100
schrieb Andrew Cooper <andrew.cooper3@citrix.com>:
> 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
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v1] automation: document how to refresh a container
2021-07-09 12:23 ` Olaf Hering
@ 2021-07-09 12:28 ` Andrew Cooper
0 siblings, 0 replies; 4+ messages in thread
From: Andrew Cooper @ 2021-07-09 12:28 UTC (permalink / raw)
To: Olaf Hering; +Cc: xen-devel, Doug Goldstein
On 09/07/2021 13:23, Olaf Hering wrote:
> Am Fri, 9 Jul 2021 13:02:54 +0100
> schrieb Andrew Cooper <andrew.cooper3@citrix.com>:
>
>> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-07-09 12:28 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-08 14:56 [PATCH v1] automation: document how to refresh a container Olaf Hering
2021-07-09 12:02 ` Andrew Cooper
2021-07-09 12:23 ` Olaf Hering
2021-07-09 12:28 ` Andrew Cooper
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.