docker - Kubernetes (Windows) on an air-gap system -
i'm working in environment development boxes (windows 7) don't have direct internet access; can download device , copy files onto development box it's not stone-age.
i have setup docker toolbox, saved images, , that's working including having ability create/update swarm want evaluate kubernetes see how compares...
i have downloaded of windows components (minikube, kubectl , virtualbox .iso) , when "minikube start" returns correctly no errors.
the issue having when k8s creates it's own containers part of startup fails pull these (due no internet access).
output kubectl follows:
c:\> kubectl pods --all-namespaces namespace name ready status restarts age kube-system kube-addon-manager-minikube 0/1 containercreating 0 1h the same true when try , install dns , dashboard pods.
i can't see kubectl logs (as suggested elsewhere), , nothing "kubectl describe po" etc. have guess issue indeed can't access external registry.
looking @ yaml these components can see docker images needs follows:
gcr.io/google-containers/kube-addon-manager:v6.4-beta.1 gcr.io/google_containers/kubedns-amd64:1.8 gcr.io/google_containers/kube-dnsmasq-amd64:1.4 gcr.io/google_containers/exechealthz-amd64:1.2 gcr.io/google_containers/kubernetes-dashboard-amd64:v1.6.0 i have pulled these images down on machine has internet access, "docker save'd" them , "docker load'ed" them onto development machine , can see these images when "docker images" follows:
$ docker images repository tag image id created size gcr.io/google_containers/kubernetes-dashboard-amd64 v1.6.0 416701f962f2 4 months ago 109mb gcr.io/google-containers/kube-addon-manager v6.4-beta.1 85809f318123 4 months ago 127mb gcr.io/google_containers/kubedns-amd64 1.8 597a45ef55ec 9 months ago 57.9mb gcr.io/google_containers/kube-dnsmasq-amd64 1.4 3ec65756a89b 9 months ago 5.13mb gcr.io/google_containers/exechealthz-amd64 1.2 93a43bfb39bf 10 months ago 8.37mb gcr.io/google_containers/exechealthz-amd64 latest 93a43bfb39bf 10 months ago 8.37mb the issue kubernetes still persists though. have in desperation tried alias "gcr.io" in hosts file localhost on development box, still persists in trying connect externally.
is there way instruct k8s use locally cached versions of docker images? has else managed k8s running on air-gapped system?
thanks steve
Comments
Post a Comment