tar: kubernetes/server/bin/kube-scheduler.docker_tag: Cannot change ownership to uid 0, gid 0:

[ibit2]

Environment

• OS:linux
• Kubernetes version:v 1.13.0
• VirtualBox version:6.0
• Vagrant version:2.2.2

What I did?

vagrant up error

Messages

tar: kubernetes/server/bin/kube-scheduler.docker_tag: Cannot change ownership to uid 0, gid 0: Operation not permitted

[rootsongjc]

Can you paste the log output in details? Which steps did you see the errors?

[ibit2]

@rootsongjc

    node1: Created symlink from /etc/systemd/system/multi-user.target.wants/flanneld.service to /usr/lib/systemd/system/flanneld.service.
    node1: Created symlink from /etc/systemd/system/docker.service.wants/flanneld.service to /usr/lib/systemd/system/flanneld.service.
    node1: enable docker
    node1: Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
    node1: copy pem, token files
    node1: kubernetes/
    node1: kubernetes/server/
    node1: kubernetes/server/bin/
    node1: kubernetes/server/bin/kube-scheduler.docker_tag
    node1: tar: kubernetes/server/bin/kube-scheduler.docker_tag: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/kube-controller-manager.docker_tag
    node1: tar: kubernetes/server/bin/kube-controller-manager.docker_tag: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/kube-apiserver.docker_tag
    node1: tar: kubernetes/server/bin/kube-apiserver.docker_tag: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/kube-scheduler.tar
    node1: tar: kubernetes/server/bin/kube-scheduler.tar: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/kubelet
    node1: tar: kubernetes/server/bin/kubelet: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/hyperkube
    node1: tar: kubernetes/server/bin/hyperkube: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/mounter
    node1: tar: kubernetes/server/bin/mounter: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/kube-apiserver.tar
    node1: tar: kubernetes/server/bin/kube-apiserver.tar: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/kube-scheduler
    node1: tar: kubernetes/server/bin/kube-scheduler: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/cloud-controller-manager.docker_tag
    node1: tar: kubernetes/server/bin/cloud-controller-manager.docker_tag: Cannot change ownership to uid 0, gid 0: Operation not permitted
    node1: kubernetes/server/bin/kube-controller-manager.tar
    node1: tar: kubernetes/server/bin/kube-controller-manager.tar: Cannot change ownership to uid 0, gid 0: Operation not permitted

[rootsongjc]

Cannot change ownership to uid 0, gid 0: Operation not permitted

It seems that the tar execution failed.

[ibit2]

@rootsongjc 那咋整啊

[rootsongjc]

I can't reproduce the situation.

[Cxywzx]

我也遇到这个问题了，和用户权限有关。
问题复现：
kubernetes-vagrant-centos-cluster 所属用户为普通用户，而用root用户执行vagrant up，过程中就会出现这个问题。
解决：
都用同一个用户，比如root用户执行，
chown -R root:root kubernetes-vagrant-centos-cluster
vagrant up
无此错误。

[Cxywzx]

uid 0, gid 0 表示使用root用户执行的
而我新建的普通用户 uid=1000

[samacs]

Just in case anyone runs into the same problem, the issue is that when the untar happens it keeps the same ownership and permissions.

I fixed the problem thanks to this post changing the line 137:

tar -xzvf /vagrant/kubernetes-server-linux-amd64.tar.gz -C /vagrant

to:

tar -xzvf /vagrant/kubernetes-server-linux-amd64.tar.gz --no-same-owner -C /vagrant

Note the --no-same-owner switch before -C /vagrant.

@rootsongjc Thank you so much for putting this thing together. Awesome!

[rootsongjc]

@samacs Can you file a PR to fix this problem, thank you.

[samacs]

@rootsongjc Sure! I'm just trying to figure out if this would happen on any platform. But I definitely will!