Push containers to registries

[michaelsauter]

We could extend Crane with a push command and the manifest with registries:

"registries": {
  "one": {},
  "two": {}
}

And then you could use it like that: crane push --registry one.

[jsierles]

This seems useful - I'm using crane now on a build server and a production release area. The push step is what now takes up the most time. Would this mean removing the registry name from the image?

[michaelsauter]

Nice to hear that Crane is used elsewhere!

I'm not a 100% sure what you mean by by "the push step is what now takes up the most time". The idea here was to allow the user to push all containers at the same time to a registry (instead of having to do that one by one). So the idea is just to wrap docker push in a similar fashion to what Crane does to docker start for example.

Is that what you thought as well or do you have a different idea?

[jsierles]

Yep this is what I'd use it for. The only question is whether the registry URL would still be included in the image name, like: "myprivateregistry.local:reponame"

[michaelsauter]

Ah, now I see what you meant. I implemented (very) basic push support in da90ec6 now. I realised we don't need a separate registries configuration to start with. Also, I don't want to add passwords to the file anyway.

However, it might make sense to be able to specify email and username in the config, and then add a password option to the push command. What I haven't figured out yet is how that would work when you've got multiple registries (which right now is possible). Ideally, there should be a way to use the push command non-interactively.

[michaelsauter]

Closing for now. Any improvements can be discussed in a separate issue.