-
Notifications
You must be signed in to change notification settings - Fork 31
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
bazel build issues #1083
Comments
bump! |
@jsakil14 have you tried the |
I just run the |
We should update the readme, but also running the |
https://github.com/kubev2v/forklift#runing-operator-build I followed this - I dont have REGISTRY_ORG , so ignored this... export REGISTRY=internal artifcatory local registry My install is on a kubevirt cluster running on bare metal k8s nodes. bazel version bazel 7.3.2 From the error: Do we need to set this values? somewhere?
|
@jsakil14 if you have some problems with the bazel please try the new dockerfiles, I have not tested them personally but they should correspond to the forklift bazel build. We are slowly moving away from bazel so some stuff might be broken. |
Could you guide me on how to install using dockerfiles? I installed forklift using olm and not with bazel. @mnecas |
I had to run it like below bazel run push-forklift-operator --@io_bazel_rules_docker//transitions:enable=false then it works! |
Is this expected? I am building image file using podman...
|
Discussed in https://github.com/orgs/kubev2v/discussions/1082
Originally posted by jsakil14 October 3, 2024
I am getting errors: when running below
The text was updated successfully, but these errors were encountered: