Initial implementation for acpush

[cgonyeo]

Currently supports performing meta discovery to find appropriate endpoint, and pushing provided image and signature to the server. Relies on rkt's config files for authentication.

[cgonyeo]

Implements client side of appc/spec#418

[cgonyeo]

Should be ready for another pass

[cgonyeo]

Another pass on this would be great.

[jonboulle]

@steveej review?

[cgonyeo]

$ bundle --version
Bundler version 1.7.6
$ gem --version
2.4.5
$ rake
rake aborted!

Perhaps disable travis on this repo for the time being?

[jonboulle]

changed travis to only build if .travis.yml is supplied

[cgonyeo]

Removed the binary, reformatted the README to have one sentence per line, and tweaked the build instructions in the REAME. Should be ready for another pass @steveej.

[cgonyeo]

ping?

[steveej]

LGTM if it works

[philips]

The idea is that this will be a library for use by rkt, right?

[cgonyeo]

Yes, if rkt gains the ability to export an exited container's rootfs. I think it makes more sense to put it in acbuild, if only because that's the tool that modifies images, and pushing unmodified images doesn't sound particularly exciting.

[philips]

I think rkt should have push/pull because it makes it symmetric. I see the
process as build with your build tool, fetch/import into rkt, push from rkt.

On Sat, Feb 6, 2016 at 2:35 PM Derek Gonyeo [email protected]
wrote:

Yes, if rkt gains the ability to export an exited container's rootfs. I
think it makes more sense to put it in acbuild, if only because that's the
tool that modifies images, and pushing unmodified images doesn't sound
particularly exciting.

—
Reply to this email directly or view it on GitHub
#1 (comment).