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

opeat: No such file or directory #503

Closed
jberkus opened this issue Oct 27, 2016 · 2 comments
Closed

opeat: No such file or directory #503

jberkus opened this issue Oct 27, 2016 · 2 comments

Comments

@jberkus
Copy link

jberkus commented Oct 27, 2016

Not sure if this is the same issue @jasonbrooks encountered, but I'm not able to install kubeadm using pkg-add as of today's Centos Continuous:

-bash-4.2# rpm-ostree pkg-add kubelet kubeadm kubectl kubernetes-cni
Checking out tree 51e65cb... done

Downloading metadata: [======================================================================================================================================================================================] 100%
Resolving dependencies... done
Overlaying... error: Unpacking kubernetes-cni-0.3.0.1-0.07a8a2.x86_64: openat: No such file or directory

@jasonbrooks
Copy link
Contributor

@jberkus Yes, this is the issue I encountered. kubernetes-cni puts files in /opt and rpm-ostree won't abide that. See #233.

I made my own kube pkgs that don't use /opt in a copr: https://gist.github.com/jasonbrooks/5d25118fa64d52af067b8fc14453c8bc. My changes: kubernetes/release@master...jasonbrooks:atomic

I have one snag remaining, the network plugins expect to find the cni binaries in opt, but I think I can tweak the weave, et al yaml to address that.

@cgwalters
Copy link
Member

Yeah, dupe of #233.

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

3 participants