All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Dario Faggioli <dfaggioli@suse.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	<xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH] ci: install C++ in opensuse-leap CI container
Date: Fri, 2 Aug 2019 13:11:27 +0100	[thread overview]
Message-ID: <b6b94de3-9fb5-5df4-81b6-60028033f985@citrix.com> (raw)
In-Reply-To: <40213dac0d5d431c4cbc39efdeab23a222ddcc90.camel@suse.com>

On 02/08/2019 13:00, Dario Faggioli wrote:
> On Mon, 2019-07-29 at 12:18 -0500, Doug Goldstein wrote:
>> On 7/26/19 5:03 AM, Dario Faggioli wrote:
>>
>>> The openSUSE Leap container image, built after
>>> opensuse-leap.dockerfile was missing the gcc-c++,
>>> which is necessary, e.g., for building OVMF.
>>>
>>> Add it.
>>>
>>> Signed-off-by: Dario Faggioli <dfaggioli@suse.com>
>>> ---
>>> Cc: Doug Goldstein <cardoe@cardoe.com>
>>> ---
>> Acked-by: Doug Goldstein <cardoe@cardoe.com>
>>
> Hey, sorry, I missed this mail. Thanks for the Ack.
>
>> Will you be pushing the rebuilt container or do you need me to do
>> that?
>>
> I tried to push, but:
>
> $ PUSH=1 make suse/opensuse-leap
> docker build -t registry.gitlab.com/xen-project/xen/suse:opensuse-leap -f suse/opensuse-leap.dockerfile suse
> Sending build context to Docker daemon  4.608kB
> Step 1/7 : FROM opensuse/leap
>  ---> dd4bf894d243
> Step 2/7 : LABEL maintainer.name="The Xen Project"       maintainer.email="xen-devel@lists.xenproject.org"
> ...
> ...
> ...
> Successfully built c78388ff370b
> Successfully tagged registry.gitlab.com/xen-project/xen/suse:opensuse-leap
> The push refers to repository [registry.gitlab.com/xen-project/xen/suse]
> 007cb8c7f305: Preparing 
> b399fccb00f7: Preparing 
> 70ea1f18573b: Preparing 
> 2379cf7101e2: Preparing 
> denied: requested access to the resource is denied
> make: *** [Makefile:14: suse/opensuse-leap] Error 1
>
> :-)
>
> So, I guess someone else, with enough rights, would have to do that.
>
> Or am I missing some auth step or aomething?

You need to do a docker login to the registry.

See https://gitlab.com/help/user/project/container_registry

Then the push should work.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-08-02 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 10:03 [Xen-devel] [PATCH] ci: install C++ in opensuse-leap CI container Dario Faggioli
2019-07-29 17:18 ` Doug Goldstein
2019-08-02 12:00   ` Dario Faggioli
2019-08-02 12:11     ` Andrew Cooper [this message]
2019-08-02 14:37       ` Dario Faggioli
2019-08-03 14:36         ` Doug Goldstein

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=b6b94de3-9fb5-5df4-81b6-60028033f985@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=dfaggioli@suse.com \
    --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.