bazelbuild / bazelbuild/rules_docker

rules_nodejs and rules_docker conflict

Open
#2,265 1 comment 0 reactions 0 assignees View on GitHub
Can Close?
Dominant language
Starlark
Stars
1.1k
Forks
689
PR merge metrics
No merged PRs in 30d

Description

# 🐞 bug report

### Affected Rule

The issue is caused by the rule:
WORKPSACE.bazel
```
oad("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
name = "build_bazel_rules_nodejs",
# Replace with a real SHA256 checksum
sha256 = "{SHA256}"
# Replace with a real release version
urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/{VERSION}/rules_nodejs-{VERSION}.tar.gz"],
)

load("@build_bazel_rules_nodejs//:index.bzl", "npm_install")

# Install your declared Node.js dependencies
npm_install(
name = "npm",
package_json = "//:package.json",
yarn_lock = "//:yarn.lock",
)

load(
"@io_bazel_rules_docker//repositories:repositories.bzl",
container_repositories = "repositories",
)

container_repositories()

load(
"@io_bazel_rules_docker//nodejs:image.bzl",
_nodejs_image_repos = "repositories",
)

_nodejs_image_repos()

```

### Is this a regression?

Yes, the previous version in which this bug was not present was: ....

### Description

## 🔬 Minimal Reproduction

```bash
bazel clean --expunge && bazel sync
```

## 🔥 Exception or Error

renguizhou@renguidembp backend % bazel clean --expunge && bazel sync

Starting local Bazel server and connecting to it...
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
Starting local Bazel server and connecting to it...
ERROR: ErrorInfo{exception=null, cycles=[[] -> [[/Users/renguizhou/Desktop/haystack/zaplink/backend]/[WORKSPACE.bazel], 2, KeyForWorkspace{label=@build_bazel_rules_nodejs//:index.bzl, isBuildPrelude=false}, KeyForWorkspace{label=@build_bazel_rules_nodejs//internal/pkg_web:pkg_web.bzl, isBuildPrelude=false}, KeyForWorkspace{label=@rules_nodejs//nodejs:providers.bzl, isBuildPrelude=false}, CONTAINING_PACKAGE_LOOKUP:@rules_nodejs//nodejs, PACKAGE_LOOKUP:@rules_nodejs//nodejs, REPOSITORY_DIRECTORY:@rules_nodejs]], isCatastrophic=false, isDirectlyTransient=false, isTransitivelyTransient=false}
checking cached actions

## 🌍 Your Environment

**Operating System:**

  

ProductName: macOS
ProductVersion: 13.4.1
ProductVersionExtra: (c)
BuildVersion: 22F770820d

**Output of `bazel version`:**

  

Build label: 6.3.1-homebrew
Build target: bazel-out/darwin_arm64-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Jan 1 00:00:00 1980 (315532800)
Build timestamp: 315532800
Build timestamp as int: 315532800

**Rules_docker version:**

  

v0.25.0

**Anything else relevant?**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.