Warning notice from docker about the image origin for etcd

juju-solutions / layer-flannel

0 stars 2 forks source link

Warning notice from docker about the image origin for etcd #21

Closed lazypower closed 8 years ago

lazypower commented 8 years ago

Originally filed by @samnco here: https://github.com/juju-solutions/layer-etcd/issues/41

When installing k8s + etcd:

k8s: gcr.io/google_containers/etcd: this image was pulled from a legacy registry.  Important: This registry version will not be supported in future versions of docker.

It seems to be related to the API version (v1). If the etcd is not republished with a v2 api this image might fail pulling unless a tag is added in the docker pull command.

lazypower commented 8 years ago

As we have no control over the GCR.io registry, and v1 registries will be fully deprecated as of docker 1.13, this does pose an interesting problem.

We will either need to

Mirror these images on the docker hub for our usage (cheap)
Stand up a v2 registry to serve these ourselves (expensive)
Ask google to update their registry to a v2 compliant registry (external dependency)

Not sure where to go with this one just yet, so i'm marking this issue as a question to be revisited.

lazypower commented 8 years ago

This appears to be resolved with the kubernetes-master and kubernetes-worker split branches where we move to binary delivery.