Yes. On Fri, Jun 10, 2016, 8:50 PM Rodrigo Campos <[email protected]> wrote:
> Great! > > What procedure did you follow in the end? Running kubernetes via docker? > > > On Friday, June 10, 2016, Manoj Khotele <[email protected]> > wrote: > >> The links are accessible indeed. >> >> But believe me those were not. >> And I am no longer getting errror like previously posted; >> >> Unable to find image 'gcr.io/google_containers/hyperkube-amd64:v1.2.4' >> locally >> >> v1.2.4: Pulling from google_containers/hyperkube-amd64 >> >> 81cc5f26a6a0: Retrying in 1 seconds >> >> a3ed95caeb02: Retrying in 1 seconds >> >> 063437597255: Downloading >> >> b4020ee389e8: Waiting >> >> 7c14ee763485: Waiting >> >> aa36c4e87d5c: Waiting >> >> 495240b55291: Waiting >> >> 1b60dd353d87: Waiting >> >> aa83270d387c: Waiting >> >> 554fc90ecd28: Waiting >> >> da1953673d52: Waiting >> >> 972445432707: Waiting >> >> bd11385d337b: Waiting >> >> f5d98b85353f: Waiting >> >> 6b117729bb3d: Waiting >> >> docker: Forbidden. >> >> See 'docker run --help'. >> >> >> Now I can have a local cluster successfully running. >> Thanks. >> >> On Wednesday, June 8, 2016 at 4:45:06 PM UTC+2, Robert Bailey wrote: >>> >>> It's accessible from a browser, but the file doesn't render in your >>> browser (it downloads) as the content type is set >>> to application/octet-stream. >>> >>> On Wed, Jun 8, 2016 at 5:32 AM, Rodrigo Campos <[email protected]> >>> wrote: >>> >>>> I can access it perfectly. Can't you? From your computer or from inside >>>> the container or something? >>>> >>>> That url just works for me, from different parts of the world I just >>>> tried (Ireland, UK and Argentina) >>>> >>>> Isn't there something else, like maybe from inside a VM or something >>>> that adds some possible failure? Or just a typo? >>>> >>>> Sorry, I can't think of anything else >>>> >>>> >>>> On Wednesday, June 8, 2016, Manoj Khotele <[email protected]> >>>> wrote: >>>> >>>>> What I mean by not-accessible is that, the link " >>>>> https://storage.googleapis.com/kubernetes-release/release/stable.txt"; >>>>> cannot >>>>> be reached through a browser as well. >>>>> >>>>> I have also ensured that the user has sudo access and is included in >>>>> docker group. >>>>> >>>>> On Tuesday, June 7, 2016 at 10:19:46 PM UTC+2, Robert Bailey wrote: >>>>>> >>>>>> What do you mean they aren't reachable? >>>>>> >>>>>> $ curl >>>>>> https://storage.googleapis.com/kubernetes-release/release/stable.txt >>>>>> v1.2.4 >>>>>> $ curl >>>>>> https://storage.googleapis.com/kubernetes-release/release/latest.txt >>>>>> v1.3.0-alpha.5 >>>>>> >>>>>> Have you configured docker users? If not, you may need to run `sudo >>>>>> docker ...` >>>>>> >>>>>> >>>>>> On Tue, Jun 7, 2016 at 12:45 AM, Manoj Khotele < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Now I am trying the option suggested by you i.e. Running Kubernetes >>>>>>> Locally via Docker. >>>>>>> But again this is not helping. >>>>>>> >>>>>>> The following links mentioned on the page are not reachable: >>>>>>> >>>>>>> https://storage.googleapis.com/kubernetes-release/release/stable.txt >>>>>>> >>>>>>> https://storage.googleapis.com/kubernetes-release/release/latest.txt >>>>>>> >>>>>>> >>>>>>> If I try for specific version, let's say v1.2.4, by running "export >>>>>>> K8S_VERSION=v1.2.4", and then running the script, it results in error >>>>>>> again. >>>>>>> >>>>>>> Unable to find image ' >>>>>>> gcr.io/google_containers/hyperkube-amd64:v1.2.4' locally >>>>>>> >>>>>>> v1.2.4: Pulling from google_containers/hyperkube-amd64 >>>>>>> >>>>>>> 81cc5f26a6a0: Retrying in 1 seconds >>>>>>> >>>>>>> a3ed95caeb02: Retrying in 1 seconds >>>>>>> >>>>>>> 063437597255: Downloading >>>>>>> >>>>>>> b4020ee389e8: Waiting >>>>>>> >>>>>>> 7c14ee763485: Waiting >>>>>>> >>>>>>> aa36c4e87d5c: Waiting >>>>>>> >>>>>>> 495240b55291: Waiting >>>>>>> >>>>>>> 1b60dd353d87: Waiting >>>>>>> >>>>>>> aa83270d387c: Waiting >>>>>>> >>>>>>> 554fc90ecd28: Waiting >>>>>>> >>>>>>> da1953673d52: Waiting >>>>>>> >>>>>>> 972445432707: Waiting >>>>>>> >>>>>>> bd11385d337b: Waiting >>>>>>> >>>>>>> f5d98b85353f: Waiting >>>>>>> >>>>>>> 6b117729bb3d: Waiting >>>>>>> >>>>>>> docker: Forbidden. >>>>>>> >>>>>>> See 'docker run --help'. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Monday, June 6, 2016 at 5:37:46 PM UTC+2, Robert Bailey wrote: >>>>>>>> >>>>>>>> To run that script you will need to clone the github repository >>>>>>>> rather than download a release (it's designed for developers). Also >>>>>>>> note >>>>>>>> that if you try to run it from the HEAD of the master branch in git you >>>>>>>> will likely run into >>>>>>>> https://github.com/kubernetes/kubernetes/issues/26453. >>>>>>>> >>>>>>>> If you want to run a release locally, have you tried Running >>>>>>>> Kubernetes Locally via Docker >>>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fkubernetes.io%2Fdocs%2Fgetting-started-guides%2Fdocker%2F&sa=D&sntz=1&usg=AFQjCNEJnKc-hPczutXxDP26T4can09Amw> >>>>>>>> ? >>>>>>>> >>>>>>>> On Mon, Jun 6, 2016 at 7:29 AM, Manoj Khotele < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> I am following Running Kubernetes Locally with No VM >>>>>>>>> <http://kubernetes.io/docs/getting-started-guides/locally/> to >>>>>>>>> start a kubernetes cluster on local linux machine in VM. >>>>>>>>> >>>>>>>>> As per this link, after downloading kubernetes, I have to run >>>>>>>>> >>>>>>>>> cd kubernetes >>>>>>>>> hack/local-up-cluster.sh >>>>>>>>> >>>>>>>>> But this fails, as kubernetes directory contains no sub-directory >>>>>>>>> "hack". >>>>>>>>> I tried this with v1.2.4; and also with v1.3.0-alpha.5. >>>>>>>>> >>>>>>>>> What am I doing wrong? >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> Manoj >>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "Containers at Google" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to [email protected]. >>>>>>>>> To post to this group, send email to [email protected]. >>>>>>>>> Visit this group at >>>>>>>>> https://groups.google.com/group/google-containers. >>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Containers at Google" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> To post to this group, send email to [email protected]. >>>>>>> Visit this group at >>>>>>> https://groups.google.com/group/google-containers. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Containers at Google" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to >>>>> [email protected]. >>>>> Visit this group at https://groups.google.com/group/google-containers. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Containers at Google" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://groups.google.com/group/google-containers. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Containers at Google" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/google-containers. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Containers at Google" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-containers/a-Rjr_bQkuA/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-containers. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
