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

rpc error: code = 2 desc = "containerd: container did not start before the specified timeout" #3265

Closed
jmarver opened this issue Jan 5, 2017 · 2 comments

Comments

@jmarver
Copy link

jmarver commented Jan 5, 2017

We've seen this error a couple of times over the last week:
rpc error: code = 2 desc = "containerd: container did not start before the specified timeout"

https://app.shippable.com/runs/58643114e18a291000c2db8d/1/console
https://app.shippable.com/runs/586e9cf49a67460f0095452d/1/console

@stephanielingwood
Copy link

Hi @jmarver,

Thanks for letting us know. While we don't see it that often, this is a known issue with Docker 1.11.1, which is what is in the unstable machine image. If you're able to use the stable machine image, that's using 1.9.1, and isn't prone to this error (as far as we know). If you decide to switch machine images, that can be done in the Subscription Settings tab.

Hope this helps. Let us know if you have any other questions.

@jmarver
Copy link
Author

jmarver commented Jan 6, 2017

Hi @stephanielingwood,

Thanks for the reply and the additional information. Yes, we're able to switch back to using the stable machine image, Docker 1.9.1.

We were hoping to use Docker 1.11.1 to take advantage of wildcard support in .dockerignore files but we can use a workaround until Shippable deems Docker 1.11.1 or newer to be stable.

Thanks again.

@jmarver jmarver closed this as completed Jan 6, 2017
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