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

k8s deploy scope error invalid argument #3154

Open
zhangll1990 opened this issue May 2, 2018 · 7 comments
Open

k8s deploy scope error invalid argument #3154

zhangll1990 opened this issue May 2, 2018 · 7 comments
Labels
mystery We don't know what could be causing this

Comments

@zhangll1990
Copy link

zhangll1990 commented May 2, 2018

in my k8s deploy scope use https://www.weave.works/docs/scope/latest/installing/#k8s
but some error occurrence
i have some nodes but just three node running,other is ImageInspectError
error : readlink /var/lib/docker/overlay2: invalid argument

@zhangll1990 zhangll1990 changed the title k8s k8s deploy scope May 2, 2018
@zhangll1990 zhangll1990 reopened this May 2, 2018
@zhangll1990 zhangll1990 changed the title k8s deploy scope k8s deploy scope error invalid argument May 2, 2018
@bboreham
Copy link
Collaborator

This looks the same as #3144 - it's an error from Docker. Maybe that node is corrupt?

@bboreham bboreham added the mystery We don't know what could be causing this label May 29, 2018
@Deepak1100
Copy link

Hi,
I am getting the same error in all the nodes. and all other pods are working I tried pulling some new image those are also working. i think its some problem with weave-scope image

@dholbach
Copy link
Contributor

dholbach commented Mar 25, 2019

The issue seen by @Deepak1100 is #3585.

(Does moby/moby#35747 have anything to do with this?)

@Deepak1100
Copy link

Hi @dholbach
i am pretty sure my issue is not #3587
but it is similart to moby/moby#35747.
even after build new image with scope binary in it. i am getting this issue in all the new nodes. and after this issue come all other new images also start giving this error.
But it work on existing node where i update the image from weavework to mine. i don't know whats the problelm with the new nodes.
may be weave is not yet started over the new image before it scope is starting and causing lots of issue.

@Deepak1100
Copy link

And if I try manually pulling image on the server where I am not running scope daemonset it's not giving any error in the image.
So the error probably start may be after starting weave scop as it have docker socket mounted. OR
it is the way kubernetes pulls the image.
Or it can be ubuntu 16.04 bug as i seen some one have same problem and using same os

@dholbach
Copy link
Contributor

Please ignore the scope issue I pointed to, that was obviously a mistake.

@bboreham
Copy link
Collaborator

Can we get some more information, e.g. the kubelet logs?
Also the output of uname -a on the node please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mystery We don't know what could be causing this
Projects
None yet
Development

No branches or pull requests

4 participants