Hi Rob,

I did below steps and it worked. I can see that your way automates it and
much better.

*cd ./coreos-kubernetes/multi-node/vagrant*
*vagrant ssh w1* (and repeat for other workers)

*cd /etc/systemd/system/docker.service.d*
*sudo vi 50-insecure-registry.conf*

add below line to this file
[Service]
Environment=DOCKER_OPTS='--insecure-registry="<your-private-registry-machine-ip>/24"'

*sudo systemctl stop docker*
*sudo systemctl daemon-reload*
*sudo systemctl start docker*
*sudo systemctl status docker*

*docker pull *<your-private-registry-machine-ip>*/api4docker*
should work fine now


Thank you for sharing it.
Turgos

On Thu, Jun 23, 2016 at 1:31 PM, Rob Szumski <[email protected]> wrote:

> Your vagrant box sources two pieces of user data from within the
> coreos-kubernetes repo, one for a worker and one for a controller.
>
> You can edit this user data to add in the insecure registry drop in from
> the CoreOS docs
> <https://coreos.com/os/docs/latest/registry-authentication.html#using-a-registry-without-ssl-configured>.
> Follow this gist:
>
> https://gist.github.com/robszumski/0bb7162032f48ff7c99e8ca72fad8f41
>
>  - Rob
>
> On Jun 23, 2016, at 5:54 AM, Gokhan Sevik <[email protected]> wrote:
>
> When I get the status of pods I see image is not loaded
>
> $ kubectl get pods
>
> NAME                          READY     STATUS             RESTARTS   AGE
>
> api4docker-2839975483-a5jju   0/1       ImagePullBackOff   0          10h
>
> api4docker-2839975483-m5p84   0/1       ImagePullBackOff   0          10h
>
>
> when I get the log from the first pod
>
> $ kubectl logs api4docker-2839975483-a5jju
>
> Error from server: container "api4docker" in pod "api4docker-2839975483-a5jju"
> is waiting to start: trying and failing to pull image
>
> thank you for your help in advance.
>
> On Wed, Jun 22, 2016 at 11:35 PM, Brandon Philips <
> [email protected]> wrote:
>
>> What is the error you get?
>>
>> On Wed, Jun 22, 2016 at 8:26 PM Turgos <[email protected]> wrote:
>>
>>> down votefavorite
>>> <http://stackoverflow.com/questions/37981367/kubernetes-installation-with-vagrant-coreos-and-insecure-docker-registry#>
>>>
>>> I have followed the steps at
>>> https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant.html to
>>> launch a multi-node Kubernetes cluster using Vagrant and CoreOS.
>>>
>>> But,I could not find a way to set an insecure docker registry for that
>>> environment. To be more specific, when I run
>>>
>>> kubectl run api4docker --image=myhost:5000/api4docker:latest --replicas=2 
>>> --port=8080
>>>
>>> on this set up, it tries to get the image thinking it is a secure
>>> registry. But, it is an insecure one.
>>>
>>> I appreciate any suggestions.
>>>
>>> Turgos
>>>
>>
>
>

Reply via email to