Cloud Batch job passing unexpected arguments to runnables

Google Cloud Compute Infrastructure
,
1

I have a cloud batch job which first has two runnables:

  1. execute a bash script to install pinned GPU drivers (the install_gpu_drivers = True option does not work for me as it installed CUDA13 drivers)
  2. a python script using dask to perform a data science process, using the GPUs

Since 24th February which is coincidentally when batch-cos-stable-official-20260218-01-p00 was released, the job now leaks arguments from the first bash script runnable to the second, which causes it to fail (with unrecognised arguments errors).

I can’t be the only one with this problem, yet there is no fix?

2

Actually it isn’t leaking variables, but the batch-agent is possibly passing additional variables to the second task. This is new behaviour as of 24th February: what’s going on?