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

kubernetes 1.2 and docker 1.10 errors #1289

Closed
davidewatson opened this Issue May 18, 2016 · 5 comments

Comments

Projects
None yet
4 participants
@davidewatson

davidewatson commented May 18, 2016

I have a 10-node kubernetes cluster running on AWS m3.medium instances with CoreOS. When I run the kubernetes density e2e tests, containers fail to start with the error "System error: The minimum allowed cpu-shares is 1024". The requested CPU shares is 10 for each container. I have not seen this error when using AWS m3.large instances.

I opened a ticket against docker and they believe the problem has been fixed in docker 1.11 (moby/moby#22818)

This is a blocking issue for us because it prevents us from running kubernetes density tests. Do we know when to expect a CoreOS release with docker 1.11?

@davidewatson

This comment has been minimized.

davidewatson commented May 19, 2016

From the ticket linked above, I believe this PR fixes our problem. Note that Samsung would like to pay to have this back ported to docker 1.10, or see a release of CoreOS with docker 1.11.

@philips

This comment has been minimized.

Member

philips commented May 25, 2016

@davidewatson this is set for the milestone for next week. Meaning we will look into it this week and it will release into Alpha next week.

@philips

This comment has been minimized.

Member

philips commented May 25, 2016

@davidewatson We have also been playing with running the docker engine under rkt. Here is an example service file: https://gist.github.com/philips/4ba6f9888499266b0ab09d95991e6784

@davidewatson

This comment has been minimized.

davidewatson commented Jun 7, 2016

@philips The latest released version is currently 1053.2.0. I do not see anything in the change logs to suggest that this fix has been back ported to that version. Is there a plan for when 1080.0.0 or 1066.0.0 will be available?

@crawford

This comment has been minimized.

Member

crawford commented Jun 7, 2016

@davidewatson this ended up getting pushed back to the 1080.0.0 release since it is not a trivial change. 1080.0.0 will be released on the 16th of the month. Sorry for the delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment