.NET Core GCP Cloud Run Job: Why Aren't Invocation Arguments Received?

Below is an explanation and the likely fix:

The Issue

Cloud Run Jobs let you override container fields (including arguments) per container. However, the override is applied only when the container override’s “name” exactly matches the container’s DNS‑compatible name as defined in your job’s container specification. In your code sample you’re using:

Name = "pass arguments"

The string “pass arguments” is not a valid DNS_LABEL (it contains a space) and likely does not match the container name defined in your job template. That means although you see the override “arguments” in the console (because GCP shows the attempted command line), the override isn’t affecting the process that your application inspects as its arguments. In other words, your container’s entrypoint isn’t receiving the override arguments.

The Fix

1. Match the Container Name Exactly:
   Make sure that the container override “name” exactly corresponds to the container’s name in the job template (using valid DNS_LABEL syntax – lowercase letters, digits, and hyphens only). For example, if your job’s container is defined as “pass-arguments”, then your override should be:

   CSHARPCopied
   Name = "pass-arguments"

2. Review How the Entrypoint Is Set Up:
   Keep in mind that the override “Args” replace any pre‐defined args if you set “ClearArgs” to true. Ensure that your container’s entrypoint (or command) is designed to receive and forward these arguments to your application’s main method. If your image has its own startup script that does not pass along extra command‑line arguments, your application code could end up with an empty args array.

Revised Code Example

Here’s how you might adjust your override (assuming your container is named “pass-arguments”):

CSHARPCopied
var request = new RunJobRequest
{
    JobName = JobName.FromProjectLocationJob("myproject", "region", "job-name"),
    Overrides = new RunJobRequest.Types.Overrides
    {
        ContainerOverrides =
        {
            new List<RunJobRequest.Types.Overrides.Types.ContainerOverride>()
            {
                new()
                {
                    // Use the exact container name as defined in the job spec
                    Name = "pass-arguments",  
                    ClearArgs = true,
                    Args = { new List<string> { "arg1", "arg2" } }
                }
            }
        },
        TaskCount = 1
    }
};
var response = this._cloudRunClient.RunJob(request);

Summary

The problem is most likely that the override’s container name doesn’t exactly match the name in your job’s definition (and isn’t a valid DNS_LABEL). Correcting the container name (and ensuring your entrypoint forwards these arguments) should make the override effective so that your application’s args parameter is populated as expected.