eg im testing with a

local.Command

using

sleep 20

as the create command and then setting a custom timeout of

2s

. when running in a new plain nodejs program it works as expected however in my container where im deploying with the automation api, the same resource runs the full 20 seconds and then times out with the same error as local: creating failed error: signal: killed: running "sleep 20" seems there is a problem with interuptting the child process when running via automation api