Google Batch: Setting `accelerator` directive removes docker ENTRYPOINT instructions

Bug report

As the title says, if somebody provides "accelerator" to the configuration of a process, the container of that process does not start with the pre-defined entrypoint from the dockerfile it was built from.

A "minimal" example:

entrypoint.sh:

echo "hello world"
bash $@

Dockerfile:

FROM python:3.13-slim 
# Setting up home
ENV HOME=/home/root
WORKDIR /home/root
RUN chmod 777 /home/root
COPY entrypoint.sh /home/root/entrypoint.sh
ENTRYPOINT ["/home/root/entrypoint.sh"]

Build the container and push it to Artifact Registry, say to CONTAINER_URI

example.nf:

processAc {
   container: CONTAINER_URI
   accelerator: [limit: 1, type: 'nvidia-tesla-t4']
   script:
   """
   exit 0
   """
}

processWoAc {
   container: CONTAINER_URI
   script:
   """
   exit 0
   """
}

workflow {
processAc()
processWoAc()
}

The google batch logs of processWoAc task will show the "hello world" message, but not for processAc task.

Environment

• Nextflow version: 26.04.4

Reproduce the behavior using entrypoint.sh, the Dockerfile, and example.nf, then compare the Google Batch logs for processAc and processWoAc. Trace how the accelerator setting changes container startup; done means the accelerator task also runs the Dockerfile ENTRYPOINT and prints the expected "hello world" message.