Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Appears to conflict with bazel 3.5.0 #1620

Closed
crutcher-dunnavant-techlabs opened this issue Sep 12, 2020 · 3 comments
Closed

Appears to conflict with bazel 3.5.0 #1620

crutcher-dunnavant-techlabs opened this issue Sep 12, 2020 · 3 comments
Labels
Can Close? Will close in 30 days unless there is a comment indicating why not

Comments

@crutcher-dunnavant-techlabs
Copy link

I get this error (with 0.14.2) on bazel 3.5.0, but on 3.3.1 it's fine.

ERROR: /home/crutcher/.cache/bazel/_bazel_crutcher/6b497f0d8f4c2590b427029c1f772dc1/external/io_bazel_rules_docker/container/BUILD:40:11: no such package '@bazel_tools//third_party/py/gflags': BUILD file not found in directory 'third_party/py/gflags' of external repository @bazel_tools. Add a BUILD file to a directory to mark it as a package. and referenced by '@io_bazel_rules_docker//container:build_tar_lib'
@luxe
Copy link

luxe commented Sep 16, 2020

Ran into the same problem with a bazel upgrade to 3.5.0.
I recommend using a commit of rules_docker after the latest 0.14.4 release.
See #1622 for a request of 0.14.5

@luxe luxe mentioned this issue Sep 16, 2020
Closed
@dmivankov dmivankov mentioned this issue Oct 6, 2020
Closed
@github-actions
Copy link

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!

@github-actions github-actions bot added the Can Close? Will close in 30 days unless there is a comment indicating why not label Mar 16, 2021
@github-actions
Copy link

This issue was automatically closed because it went 30 days without a reply since it was labeled "Can Close?"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Can Close? Will close in 30 days unless there is a comment indicating why not
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@luxe @crutcher-dunnavant-techlabs