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.

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

value set via BAZEL_REMOTE_HTTP_ADDRESS cannot be applied. #736

Open
zaka634 opened this issue Feb 28, 2024 · 2 comments
Open

value set via BAZEL_REMOTE_HTTP_ADDRESS cannot be applied. #736

zaka634 opened this issue Feb 28, 2024 · 2 comments

Comments

@zaka634
Copy link

zaka634 commented Feb 28, 2024

Set BAZEL_REMOTE_HTTP_ADDRESS to : 0.0.0.0:8888 on k8s yaml file for the docker image published on docker hub, version is v2.4.3

but when running the container, the log is still saying started the server on 8080, and port 8888 is never opened, debug through the code, I think this config :
https://github.com/buchgr/bazel-remote/blob/master/BUILD.bazel#L118

caused the port to be hard-coded so that it did not respect the value set for BAZEL_REMOTE_HTTP_ADDRESS. I compiled another image once removed the hard-coded value from oci_image, it just works.

@mostynb
Copy link
Collaborator

mostynb commented Feb 29, 2024

Just checking- is your bazel-remote deployment named "bazel-remote" ? If so, that might be causing this problem, because kubernetes will set some environment variables that conflict with the ones you're trying to set.

@zaka634
Copy link
Author

zaka634 commented Feb 29, 2024

no, I thought the doc saying don't name the deployment as like that, current name is "bazel-remote-cache-eng". I found the PR fix : #699.

Just build a docker image based on the oci_images:env setting, it works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants