bump debian-hyperkube-base to 0.5 since CNI gets bumped

This commit is contained in:
Di Xu 2017-10-20 10:30:44 +08:00
parent 191ff804ea
commit 7ec31b67c8
3 changed files with 4 additions and 4 deletions

View File

@ -19,7 +19,7 @@
REGISTRY?=gcr.io/google-containers
IMAGE?=debian-hyperkube-base
TAG=0.4
TAG=0.5
ARCH?=amd64
CACHEBUST?=1

View File

@ -70,10 +70,10 @@ docker_pull(
docker_pull(
name = "debian-hyperkube-base-amd64",
digest = "sha256:f3a37c4d8700a5ff454d94a2bef7d165d287759cea737a621c20e4aa3891dbbb",
digest = "sha256:d216b425004fcb6d8047f74e81b30e7ead55f73e73511ca53a329c358786b6c9",
registry = "gcr.io",
repository = "google-containers/debian-hyperkube-base-amd64",
tag = "0.4", # ignored, but kept here for documentation
tag = "0.5", # ignored, but kept here for documentation
)
docker_pull(

View File

@ -21,7 +21,7 @@ REGISTRY?=gcr.io/google-containers
ARCH?=amd64
HYPERKUBE_BIN?=_output/dockerized/bin/linux/$(ARCH)/hyperkube
BASEIMAGE=gcr.io/google-containers/debian-hyperkube-base-$(ARCH):0.4
BASEIMAGE=gcr.io/google-containers/debian-hyperkube-base-$(ARCH):0.5
TEMP_DIR:=$(shell mktemp -d -t hyperkubeXXXXXX)
all: build