-
Notifications
You must be signed in to change notification settings - Fork 75
Open
Description
When building from the main git branch with make build-all-images, the ovirt-populator image fails with the following error
/usr/bin/podman build -t quay.io/kubev2v/ovirt-populator:devel -f build/ovirt-populator/Containerfile-upstream .
[1/2] STEP 1/7: FROM registry.access.redhat.com/ubi8/go-toolset:1.23.6-2.1747189110 AS builder
[1/2] STEP 2/7: ENV GOPATH=$APP_ROOT
--> Using cache a7d126ff9d71fcde6b6105d31fdb0d14a72e7a5278662925b44250f02caf010a
--> a7d126ff9d71
[1/2] STEP 3/7: WORKDIR /app
--> Using cache 93d944a7ee60ed4a3ced04ba1e1ef159f3fca8ce5bea77995a3a6cf6001d1f9b
--> 93d944a7ee60
[1/2] STEP 4/7: COPY --chown=1001:0 ./ ./
--> b2bba7443257
[1/2] STEP 5/7: ENV GOFLAGS "-mod=vendor -tags=strictfipsruntime"
--> 571af5a3a928
[1/2] STEP 6/7: ENV GOEXPERIMENT strictfipsruntime
--> 109ef2c48f78
[1/2] STEP 7/7: RUN GOOS=linux GOARCH=amd64 go build -o ovirt-populator github.com/kubev2v/forklift/cmd/ovirt-populator
go: go.mod requires go >= 1.24.0 (running go 1.23.6; GOTOOLCHAIN=local)
Error: building at STEP "RUN GOOS=linux GOARCH=amd64 go build -o ovirt-populator github.com/kubev2v/forklift/cmd/ovirt-populator": while running runtime: exit status 1
make: *** [Makefile:328: build-ovirt-populator-image] Error 1
The ovirt-populator image seems to be the only one that still uses a go 1.23.x image. Also, I've noticed that the ovirt-populator seems to be the only image that builds against a ubi8 based image. Is this intentional or was it overlooked?
Metadata
Metadata
Assignees
Labels
No labels