-
Notifications
You must be signed in to change notification settings - Fork 275
Add possibility for the local host to act as repository. #56
Comments
It's docker in docker so you may use: where target_node is the node where you need your image (you can have script that does it automatically on all nodes) |
Handy work around, but it's not very kube-like. There should be a way to specify the repository as the local docker repo to mimic a standard workflow. |
Problem is that if you're using multiple nodes, you'll have to use some kind of docker repo, probably local one, and push images there. So are you asking about hints how to make DIND work with local docker image repository? Other possibility is to make a single-node cluster and use it's inner docker engine to build images etc. I can also give some hints how to do it if you want |
I think what were looking for is a way to do:
And have it pull the image from the local host system Docker repository, rather than Docker Hub. Which wouldn't seem that hard to arrange. Minikube seems to manages to do this. |
All I need to do is Minikube solves this by directing DOCKER_HOST to minikube's local repository. A single node DIND-cluster would work perfect, actually, running just the master, untainted, as in minikube would be a good-enough replacement for minikube (mainly what I'm after) |
I'm a kubernetes/kubeadm-dind newbie. I'm running multiple nodes on osx and this (docker build -t ...) doesn't work for me. when i run kubectl run --image foo it fails on can't find "library/foo" in the pod. I found dind::copy-image and it distributed the image, but still not able to find it. |
It would be great to serve a registry from local So a simple workaround:
Now localhost:5000 is a registry url.
docs: https://hub.docker.com/r/tecnativa/tcp-proxy/
The trick is that 127.0.0.0/8 network is in insecure registries by default. No need to init cluster with DIND_INSECURE_REGISTRIES variable and to edit /etc/docker/daemon.json. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Basically the goal is to replace minikube with this. Minikube is cpu and memory intensive and has only one master node and no workers.
The dind-approach is by far better, just not as mature.
On thing that doesn't work (or I found no way of doing it) is to build images locally without pushing them to any repository and the use them in the dind-cluster.
That would be awesome.
The text was updated successfully, but these errors were encountered: