You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
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.
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.
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
The text was updated successfully, but these errors were encountered: