Allow Ignoring of pre-loaded packages. about rules_docker HOT 6 CLOSED

Yeah, I think we can safely add a kwarg for that. I hadn't seen the rules_protobuf stuff, that has a number of interesting features.

from rules_docker.

Determined that if I changed the ordering of my linked workspaces I circumvented this issue so this is merely a nice to have at this point. Thanks!

from rules_docker.

Thank you @mattmoor!

from rules_docker.

@promiseofcake My pleasure, sorry this was a little slow.

from rules_docker.

No worries, thanks also for native.existing_rules().keys(), that is a neat trick.

from rules_docker.

Same issue when attempting to build containers in a repository that has a tensorflow dependency (which is also providing that bind for com_google_protobuf).

Here is a related issue from the parent containerregistry where this dependency originates: google/containerregistry#36. The problem is that we don't have a way to choose which @six we are providing due to the bind, and there doesn't seem to be a way to programmatically use //external:six or @six//:six.

I can get around this with a fork, kind of, the problem is that we are depending on published artifacts for puller and importer as opposed to their public targets in google/containerregistry. I attempted to swap the local http_file targets with the parent targets @containerregistry//:puller or @containerregistry//:puller.par but those aren't working.

@mattmoor, do you know why we need to use the published artifacts rather than repo's targets?

from rules_docker.