Since the exec command does not use labels from .runner, there is no existing way to specify which Docker image to use for task execution.
This adds an --image flag for specifying it manually. The default remains node:16-bullseye.
Since the `exec` command does not use labels from `.runner`, there is no existing way to specify which Docker image to use for task execution.
This adds an `--image` flag for specifying it manually. The default remains `node:16-bullseye`.
Oh, maybe we should still have labels containers mapping?
I don't think so, unlike daemon, a flag is enough for exec. The user may want to test the same job on different images, so it will be convenient to use a single flag.
> Oh, maybe we should still have labels containers mapping?
I don't think so, unlike `daemon`, a flag is enough for `exec`. The user may want to test the same job on different images, so it will be convenient to use a single flag.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Since the
execcommand does not use labels from.runner, there is no existing way to specify which Docker image to use for task execution.This adds an
--imageflag for specifying it manually. The default remainsnode:16-bullseye.Oh, maybe we should still have labels containers mapping?
I don't think so, unlike
daemon, a flag is enough forexec. The user may want to test the same job on different images, so it will be convenient to use a single flag.I do not have the approval to merge, but if someone else would like to do it, sounds good to me.