operator-sdk
operator-sdk copied to clipboard
Docker builder time exploses
Bug Report
What did you do?
Upgraded to 1.39.1 of operator-sdk (go).
What did you expect to see?
Same building time for docker.
What did you see instead? Under which circumstances?
Increase of time from 15mins to 50mins of build.
Environment
Operator type:
/language go
Kubernetes cluster type:
$ operator-sdk version
1.39.1
$ go version (if language is Go)
1.24.1
Possible Solution
Rollback change introduced in 1.34.0
Additional context
I made the change introduced in 1.34.0 and the building time of the docker image increased from 15mins before to 50mins after.
The pain point is on this line: RUN CGO_ENABLED=0 GOOS=$TARGETOS GOARCH=$TARGETARCH go build -a -o manager cmd/main.go
Hi @juldrixx Are you interested in mult-arch builds? If so the make docker-buildx will build all architectures for you. If you only want single arch run make docker-build. The time increase makes sense, since the bug was only building on the plaftrom running the make command, instead of building all architectures in the list.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.