specify step when hijacking one-off builds
The new "check containers as steps change" causes there to be at least
two containers when doing a fly execute now. Previously it was always
one container and the step did not need to be specified.
@@ -59,6 +59,7 @@ func containerLimitsWork(selectorFlags ...string) {
hijackSession := fly.Start(
"hijack",
"-b", "1",
+ "-s", "one-off",
"--", "sh", "-c",
"cat /sys/fs/cgroup/memory/memory.memsw.limit_in_bytes; cat /sys/fs/cgroup/cpu/cpu.shares",
)
