Added Windows variants for v2.6.0

[sixeyed]

Added Dockerfiles for building registry images running on Windows Nano Server and Windows Server Core. The binaries were built from v2.6.0 of docker/distribution using the local source for PR 2209.

Sample images are on the Hub as sixeyed/registry. The Windows Dockerfiles are good to be built as official images with this PR.

The update.sh changes rebuild the Windows binary in the same way that the Linux binary is built. That depends on PR 2209 so it is for future releases.

[sajayantony]

/cc @jhowardmsft @aaronlehmann @shhsu @friism

[friism]

What's up @SajayAntony ?

[sajayantony]

@friism do you know who can help review these?

[sixeyed]

Bumped Windows versions, but this is still dependent on docker/distribution PR 2209.

[dazinator]

Sorry if this is the wrong place to raise these questions / concernes. Are there thoughts on how we can secure the .key file that we must mount into the container for SSL to work? If the registry service was compromised, we are worried that the private key could be stolen. On windows if you had to protect a certificate at rest (on disk) you would typically persist it as a passphrase protected pfx file. Otherwise it should be in the windows certificate store. However I am assuming that registry.exe doesn't integrate with the windows certificate store when running on windows? Is it possible to delete the .key file after the registry.exe has started (i.e is it loaded into memory and used from there for the duration) or does the .key file have to remain on disk whilst the registry.exe is running in order for SSL to work?

[drnybble]

Status? I'd like to use an official image on Windows

[John0King]

Any progress on this ? When will have offcial windows image ?

[AndreasHassing]

This would close #26.