<
8000
div
id="partial-discussion-header"
class="gh-header mb-3 js-details-container Details js-socket-channel js-updatable-content issue"
data-channel="eyJjIjoiaXNzdWU6MTQxNDQ1Mzg0IiwidCI6MTc0ODAwMDUzMH0=--0bb99ee4dd41b94bd4fe3efed2dd95a92f3b5db798a62684e7bdf9d1f5748b54"
data-url="/containerd/containerd/issues/134/show_partial?partial=issues%2Ftitle&sticky=true"
data-gid="MDU6SXNzdWUxNDE0NDUzODQ=">
The OCI specs allows for start hooks to be specified. Since those are arbitrary binaries they could take a significant amount of time rendering the current timeout use to wait for the pid file to appear (i.e. 15) to be too short.
I'd propose adding an option to allow a user to set this timeout either daemon wide (i.e. for all containers) or per container. The second option would require a change in the grpc protocol though.
The text was updated successfully, but these errors were encountered: