Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run kubernetes within boot2docker #7428

Closed
acroca opened this issue Apr 28, 2015 · 9 comments
Closed

Can't run kubernetes within boot2docker #7428

acroca opened this issue Apr 28, 2015 · 9 comments
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@acroca
Copy link

acroca commented Apr 28, 2015

I'm following the docker tutorial (https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/docker.md) but I can't make it work.

etc runs without problems, but the master shows some errors on the log: https://gist.github.com/acroca/dac7cdc196b26c6ae65d

I get the following error running containers too:

$ kubectl run-container nginx --image=nginx --port=80          
Error from server: the server could not find the requested resource (post replicationControllers)

I use boot2docker and docker 1.6.0.

@a-robinson
Copy link
Contributor

cc @brendandburns looks like the apiserver didn't come up?

@acroca
Copy link
Author

acroca commented Apr 29, 2015

Is there anything else I can do to help troubleshooting this issue?

@erictune
Copy link
Member

Those instructions seem totally broken. The step that is entitled "Run the
master" is actually running the kubelet.

On Wed, Apr 29, 2015 at 3:33 AM, Albert Callarisa notifications@github.com
wrote:

Is there anything else I can do to help troubleshooting this issue?


Reply to this email directly or view it on GitHub
#7428 (comment)
.

@erictune
Copy link
Member

Never mind, I see the comment that says "This actually runs the kubelet,
which in turn runs a pod that contains the other master components."

On Wed, Apr 29, 2015 at 9:13 AM, Eric Tune etune@google.com wrote:

Those instructions seem totally broken. The step that is entitled "Run the
master" is actually running the kubelet.

On Wed, Apr 29, 2015 at 3:33 AM, Albert Callarisa <
notifications@github.com> wrote:

Is there anything else I can do to help troubleshooting this issue?


Reply to this email directly or view it on GitHub
#7428 (comment)
.

@erictune
Copy link
Member

Okay, I followed the instructions, and my cluster came up okay. I also see
similar error messages in my logs (by the way, the logs in the gist are
from kubelet not apiserver).

acroca: what happens when you follow the next steps (setup ssh tunnel, and
then run kubectl -s http://localhost:8080 get pods)

On Wed, Apr 29, 2015 at 9:15 AM, Eric Tune etune@google.com wrote:

Never mind, I see the comment that says "This actually runs the kubelet,
which in turn runs a pod that contains the other master components."

On Wed, Apr 29, 2015 at 9:13 AM, Eric Tune etune@google.com wrote:

Those instructions seem totally broken. The step that is entitled "Run
the master" is actually running the kubelet.

On Wed, Apr 29, 2015 at 3:33 AM, Albert Callarisa <
notifications@github.com> wrote:

Is there anything else I can do to help troubleshooting this issue?


Reply to this email directly or view it on GitHub
#7428 (comment)
.

@acroca
Copy link
Author

acroca commented Apr 29, 2015

I can get the pods, nodes and so on, but the problem comes when I try to run a container, create a service or a rc.

@erictune
Copy link
Member

erictune commented May 1, 2015

I'm out next week, so I am not going to be able to work on this. Someone should try to repro this.

@Kangmo
Copy link

Kangmo commented May 11, 2015

I have the same problem. I followed instructions on examples/meteor/README.md on master branch, but deployed my k8s cluster with v0.16.2 tag.

$ docker --version
Docker version 1.6.0, build 4749651

$ boot2docker version
Boot2Docker-cli version: v1.6.0
Git commit: 9894ae9

@thockin thockin added kind/support Categorizes issue or PR as a support question. and removed kind/support Categorizes issue or PR as a support question. priority/support labels May 19, 2015
@goltermann
Copy link
Contributor

We’re going through old support issues and asking everyone to direct your questions to stackoverflow.

We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases.

We regularly see messages posted in multiple forums, with the full response thread only in one place or, worse, spread across multiple forums. Also, the large volume of support issues on github is making it difficult for us to use issues to identify real bugs.

The Kubernetes team scans stackoverflow on a regular basis, and will try to ensure your questions don't go unanswered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

6 participants