Skip to content

Commit af444c0

Browse files
authored
Mentioning problem with checksum mismatch error (#605)
1 parent b068c64 commit af444c0

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

README.md

+15
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,21 @@ cd keda
9494
make build
9595
```
9696

97+
If the build process fails due to some "checksum mismatch" errors, make sure that `GOPROXY` and `GOSUMDB` environment variables are set properly.
98+
With Go installation on Fedora, for example, it could happen they are wrong.
99+
100+
```bash
101+
go env GOPROXY GOSUMDB
102+
direct
103+
off
104+
```
105+
106+
If not set properly you can just run.
107+
108+
```bash
109+
go env -w GOPROXY=https://proxy.golang.org,direct GOSUMDB=sum.golang.org
110+
```
111+
97112
## Deploying: Custom KEDA locally outside cluster
98113
The Operator SDK framework allows you to [run the operator/controller locally](https://github.com/operator-framework/operator-sdk/blob/master/doc/user-guide.md#2-run-locally-outside-the-cluster)
99114
outside the cluster without a need of building an image. This should help during development/debugging of KEDA Operator or Scalers.

0 commit comments

Comments
 (0)