From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, <xen-devel@lists.xenproject.org>
Cc: Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH v1] automation: document how to refresh a container
Date: Fri, 9 Jul 2021 13:02:54 +0100 [thread overview]
Message-ID: <b405e7c8-44ac-56c0-8fcc-3c25ac4b3914@citrix.com> (raw)
In-Reply-To: <20210708145628.8902-1-olaf@aepfle.de>
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
>
next prev parent reply other threads:[~2021-07-09 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 14:56 [PATCH v1] automation: document how to refresh a container Olaf Hering
2021-07-09 12:02 ` Andrew Cooper [this message]
2021-07-09 12:23 ` Olaf Hering
2021-07-09 12:28 ` Andrew Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b405e7c8-44ac-56c0-8fcc-3c25ac4b3914@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.