I'm sorry, I didn't realise that in #276 I added a side-effecting call to idris2 (which may change the state of $HOME/.pack in some circumstances), which made some operations failing in a flaky way when being run under the pack's docker image, e.g. when either two calls to pack are changing same files in a non-synchronised fashion, or another utilities, like tar are detecting changes in the file system, which are unexpected to them.
So, let's change the healthcheck command to a more appropriate one -- it checks that pack runs, but help command is not side-effecting.
I'm sorry, I didn't realise that in #276 I added a side-effecting call to
idris2(which may change the state of$HOME/.packin some circumstances), which made some operations failing in a flaky way when being run under the pack's docker image, e.g. when either two calls topackare changing same files in a non-synchronised fashion, or another utilities, liketarare detecting changes in the file system, which are unexpected to them.So, let's change the healthcheck command to a more appropriate one -- it checks that
packruns, buthelpcommand is not side-effecting.