Cloud Batch job passing unexpected arguments to runnables

Google Cloud Compute Infrastructure
,
4

Hi output4616,

First, please accept our apologies for the late response and the frustration these issues caused while you were waiting for a resolution.

We have been investigating the specific behaviors you reported, and I can now provide some clarity on what happened:

  • Argument “Leaking” (Feb 24th): You were correct—an internal update intended to improve GPU driver discovery on Cloud Batch (specifically for COS images) unintentionally altered how container commands and arguments were wrapped.

  • This problematic change was rolled back, and have since deployed a permanent fix that resolves the GPU discovery issue without affecting standard container execution.

  • ENTRYPOINT Issues (March 19th): It seems that the new logic introduced a side effect causing the service to stop respecting container ENTRYPOINTs.

    Could you let us know if you are still seeing this issue today? If your jobs are still failing to respect the ENTRYPOINT or requiring manual overrides, we want to know so we can refine the logic and provide a proper fix that doesn’t require workarounds.

Thank you for your patience and for surfacing this.