Increase container start timeout #1854

Closed
rojer opened this Issue Mar 7, 2017 · 2 comments

Comments

@rojer

rojer commented Mar 7, 2017

Issue Report

Bug

Container Linux Version

# cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1298.5.0
VERSION_ID=1298.5.0
BUILD_ID=2017-02-28-0013
PRETTY_NAME="Container Linux by CoreOS 1298.5.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

Environment

Amazon EC2

Expected Behavior

Containers start every time

Actual Behavior

Sometimes containers fail to start with the following error:

docker: Error response from daemon: containerd: container did not start before the specified timeout.

Reproduction Steps

Intermittent, no good repro. I suspect this happens when a lot of containers are started at once, with increased load on the system.

Other Information

The timeout in question is controlled by the --start-timeout flag to containerd. Default for this flag is 30 seconds, and it was raised to 2 minutes several months ago (in this commit).
However, since CoreOS uses its own service to launch containerd, this was not picked up.
--start-timeout=2m should be added to containerd.service.

@dm0-

This comment has been minimized.

Show comment
Hide comment
@dm0-

dm0- Mar 15, 2017

Member

This will be in Thusday's alpha.

Member

dm0- commented Mar 15, 2017

This will be in Thusday's alpha.

@dm0- dm0- closed this Mar 15, 2017

@rojer

This comment has been minimized.

Show comment
Hide comment
@rojer

rojer Mar 15, 2017

thank you!

rojer commented Mar 15, 2017

thank you!

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