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

Minion file systems are overlay #1

Open
cortezone opened this issue Feb 26, 2015 · 2 comments
Open

Minion file systems are overlay #1

cortezone opened this issue Feb 26, 2015 · 2 comments

Comments

@cortezone
Copy link

Hi @Runseb,
I've noticed that the file system of the minions created with ansible-kubernetes is overlay and this does throw some errors when some docker commands are run on them. I also canno find the kubecfg binary on the k8 head. I'm not sure therefore how to test the cluster since kubecfg does not exist.

@sebgoa
Copy link
Member

sebgoa commented Feb 27, 2015

Hi @cortezone , yes the kubectl binary is not in there. You can get it on master with:
wget https://storage.googleapis.com/kubernetes-release/release/v0.9.1/bin/linux/amd64/kubectl

if you have it locally on your computer you can also create a SSH tunnel to the k8s master.

I will check the nodes. I was having some problems as well with overlafs, but they disappeared by using the latest coreOS release.

@cortezone
Copy link
Author

Hi @Runseb, I went through the k8s-node.js file and noted that Docker was started with the -s overlay flag which is the reason that the minions come up with docker using an overlay filesystem. Is there any particular reason for this? I had issues running containers on the overlay filesystem. Would it be necessary to pull this to fix it?
@cortezone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants