'container did not start before the specified timeout' ERRORS during docker-puppet config generation
Bug #1713188 reported by
Dan Prince
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Dan Prince |
Bug Description
I've been getting errors like this when pulling images from a local Undercloud registry (heavily loaded during provisioning):
containerd: container did not start before the specified timeout.",
----
I tried setting the PROCESS_COUNT back to 3 (which matches docker daemon's pull default as well) and all issues went away.
Changed in tripleo: | |
assignee: | nobody → Dan Prince (dan-prince) |
importance: | Undecided → High |
status: | New → In Progress |
milestone: | none → pike-rc2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/498139
Review: https:/