Add `extra_deps` attribute to `container_run_and_commit`*

[dpward]

#1003 (with a follow-up fix in #1933) added an extra_deps attribute to container_run_and_extract:

rules_docker/docker/util/run.bzl

Lines 58 to 61 in 1bb136e

	extra_deps: Label list, if not None these are passed as inputs
	to the action running the container. This can be used if
	e.g., you need to mount a directory that is produced
	by another action.

The attribute is needed by container_run_and_commit and container_run_and_commit_layer for exactly the same reason.

[njlr]

Is it not possible to chain together container_run_and_commit_layer and container_image?

For example

container_image(
  name = "stage_1",
  tars = [
    ":app",
  ],
)

container_run_and_commit_layer(
  name = "stage_2",
  image = ":stage_1.tar",
  commands = [ "setup.sh" ],
)

[dpward]

Assume that setup.sh requires a file to be mounted in the container (i.e. with docker -v). The dependency which generates that file should be specified directly in container_run_and_commit_layer.

It can be expensive to run container_image. We don't need to call it for the sole purpose of making sure a dependency is satisfied for an independent rule. (Consider that the container image may already exist.)

[manuelnaranjo]

FYI #2209

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!

[dpward]

/remove-labels "Can Close?"

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!