Host OS updates fail from 2.3.0 directly to 2.31.5, but 2.3.0->2.15.1->2.31.5 succeeds, and the first step of the two-step update should be the same kind of in-container update as the aforementioned one. Why's that? What changed in the update hooks mechanism between 2.15.1 and 2.31.5 that can explain this?
Log segment:
Starting hostapp-update
time="2019-05-23T14:29:37.002634755Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/containers/create type="*events.ContainerCreate"
time="2019-05-23T14:29:37Z" level=info msg="shim balena-engine-containerd-shim started" address=/containerd-shim/moby/ff21bb4e14ea135a4960c6ab66cdd4097a1ff4f7f471dc922374c154dba57742/shim.sock debug=false module=containerd/tasks pid=159
time="2019-05-23T14:29:37Z" level=info msg="shim reaped" id=ff21bb4e14ea135a4960c6ab66cdd4097a1ff4f7f471dc922374c154dba57742 module=containerd/tasks
time="2019-05-23T14:29:37.684380313Z" level=error msg="stream copy error: reading from a closed fifo"
time="2019-05-23T14:29:37.686453397Z" level=error msg="stream copy error: reading from a closed fifo"
time="2019-05-23T14:29:37.706128433Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/containers/delete type="*events.ContainerDelete"
time="2019-05-23T14:29:37.764954562Z" level=warning msg="Failed to delete conntrack state for 10.114.201.128: invalid argument"
time="2019-05-23T14:29:38.111243805Z" level=error msg="ff21bb4e14ea135a4960c6ab66cdd4097a1ff4f7f471dc922374c154dba57742 cleanup: failed to delete container from containerd: no such container"
time="2019-05-23T14:29:38.239213776Z" level=error msg="Handler for POST /v1.35/containers/ff21bb4e14ea135a4960c6ab66cdd4097a1ff4f7f471dc922374c154dba57742/start returned error: OCI runtime create failed: container_linux.go:296: starting container process caused \"process_linux.go:297: copying bootstrap data to pipe caused \\\"write init-p: broken pipe\\\"\": unknown"
balena: Error response from daemon: OCI runtime create failed: container_linux.go:296: starting container process caused "process_linux.go:297: copying bootstrap data to pipe caused \"write init-p: broken pipe\"": unknown.
Failed to run the new hooks...
Host OS updates fail from 2.3.0 directly to 2.31.5, but 2.3.0->2.15.1->2.31.5 succeeds, and the first step of the two-step update should be the same kind of in-container update as the aforementioned one. Why's that? What changed in the update hooks mechanism between 2.15.1 and 2.31.5 that can explain this?
Log segment: