bugs icon indicating copy to clipboard operation
bugs copied to clipboard

docker at coreos fails to start after unmounting errors of /run/torcx/unpack during reboot

Open doets001 opened this issue 5 years ago • 0 comments

Issue Report

Bug

Container Linux Version

$ cat /etc/os-release NAME="Container Linux by CoreOS" ID=coreos VERSION=2191.5.0 VERSION_ID=2191.5.0 BUILD_ID=2019-09-04-0357 PRETTY_NAME="Container Linux by CoreOS 2191.5.0 (Rhyolite)" ANSI_COLOR="38;5;75" HOME_URL="https://coreos.com/" BUG_REPORT_URL="https://issues.coreos.com" COREOS_BOARD="amd64-usr"

Environment

We run the coreos in vmware ESXi virtuals.

Expected Behavior

After an update of coreos we expect all docker to start automatically. That is the situation in 99% of the upgraded of our coreos hosts.

Actual Behavior

with every coreos update of the 200 core's systems we have 1 or 2 random systems which do niet start after the boot. That is, it will start, but the docker containers do not start because torcx didn't add docker and so docker is not available

Reproduction Steps

We are not able to reproduce this, but this happens for a long time now. I guess more than a year.

Other Information

I logged more detail in https://github.com/coreos/torcx/issues/130

doets001 avatar Sep 26 '19 11:09 doets001