Skip to content

Fix container and K3S tests

Adam Johnston requested to merge adam.johnston2/meta-cassini:topics/CAS-112 into mickledore-dev

We see a problem when the docker CLI is invoked via sudo from BATS scripts where the CLI thread seems to get stuck in a loop, trying to kill a container after it has already stopped.

We don't know what the root cause is yet, but it seems to be due to some terminal handling interaction between the docker CLI and the BATS core. Background processes are known to complicate BATS terminal handling and sudo complicates it further. It appears we can avoid the problem by either

  • refactoring to avoid sudo
  • dropping the interactive option from the container connectivity test

We do latter (for now) because:

  • the interactive option is not required for this specific test
  • investigating the root cause is likely to be non-trivial

This change fixes both container and K3S tests

Signed-off-by: Adam Johnston adam.johnston@linaro.org

Merge request reports