[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] Buildah and "docker login"

Hi //D.S

    Dan Walsh just pinged me and forwarded the below e-mail to me.  I've just joined the atomic-devel list so hopefully this will make it's way to the right spots.

    Short story is with Buildah you currently still need to use 'docker login' in order to authenticate to a private registry.  I do however have a PR (https://github.com/projectatomic/buildah/pull/204) winding it's way through the review process to do authentication for 'buildah from'.  I need to rebase it due to a merge conflict that happened a little bit ago and get it back out for review.  I'm hoping to get that code into play in the next day or two. 

    That PR has the changes necessary for buildah from and most if not all the utilities needed to easily add the authentication capabilities to the push and commit commands.  I'm really hoping to wrap it all up late this week, but it might leak into next week. 

    If you've a github username that  you can send me, I'd be happy to post a comment containing your name in it for this or other upcoming authentication commits for Buildah.

    Best Wishes!


On 08/14/2017 02:07 PM, Daniel Walsh wrote:

-------- Forwarded Message --------
Subject: [atomic-devel] Buildah and "docker login"
Date: Mon, 14 Aug 2017 19:55:38 +0200
From: D.S. Ljungmark <ljungmark modio se>
To: atomic-devel <atomic-devel projectatomic io>

Hi all,
  So we're investigating migrating away from docker to build our
containers, and towards buildah instead.

So far, building appears to work, which is all very good, but I haven't
yet found a way to do the `docker login` step.  As far as I know, it's
an Oauth2 login with scopes set,  and then stored as a json object.

However, because of how docker works, I'd still have to run a docker
daemon just to log in with each CI build,  which makes buildah a pretty
pointless exercise for me.

So, does anyone have a good resource of how to achieve a proper
config.json, or other authentication, to allow `buildah push` to publish
to a private registry?

8362 CB14 98AD 11EF CEB6  FA81 FCC3 7674 449E 3CFC

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]