[GH-ISSUE #987] Issue: Installation fails with "unknown revision v0.20.6" (for k8s.io/apiserver@v0.20.6) #580

Closed
opened 2026-03-01 21:44:42 +03:00 by kerem · 11 comments
Owner

Originally created by @sschuberth on GitHub (Feb 9, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/987

System information

  • Operating System: Fedora 34
  • Architecture: x64 (64-bit)
  • Apple M1: no
  • Docker version: 20.10.12
  • Docker image used in act: n/a
  • act version: latest

Expected behaviour

Installation should succeed via go install github.com/nektos/act@latest.

Actual behaviour

Installation fails with

$ go install github.com/nektos/act@latest
go: downloading github.com/nektos/act v0.2.25
go install github.com/nektos/act@latest: github.com/nektos/act@none updating to
        github.com/nektos/act@v0.2.25 requires
        github.com/containerd/containerd@v1.5.5 requires
        k8s.io/apiserver@v0.20.6: reading k8s.io/apiserver/go.mod at revision v0.20.6: unknown revision v0.20.6

Workflow and/or repository

n/a

Steps to reproduce

See above.

act output

n/a

Originally created by @sschuberth on GitHub (Feb 9, 2022). Original GitHub issue: https://github.com/nektos/act/issues/987 ## System information - Operating System: Fedora 34 - Architecture: x64 (64-bit) - Apple M1: no - Docker version: 20.10.12 - Docker image used in `act`: n/a - `act` version: latest ## Expected behaviour Installation should succeed via `go install github.com/nektos/act@latest`. ## Actual behaviour Installation fails with ``` $ go install github.com/nektos/act@latest go: downloading github.com/nektos/act v0.2.25 go install github.com/nektos/act@latest: github.com/nektos/act@none updating to github.com/nektos/act@v0.2.25 requires github.com/containerd/containerd@v1.5.5 requires k8s.io/apiserver@v0.20.6: reading k8s.io/apiserver/go.mod at revision v0.20.6: unknown revision v0.20.6 ``` ## Workflow and/or repository n/a ## Steps to reproduce See above. ## `act` output n/a
kerem 2026-03-01 21:44:42 +03:00
  • closed this issue
  • added the
    kind/bug
    label
Author
Owner

@catthehacker commented on GitHub (Feb 9, 2022):

Can you show output of go env?
That revision still exists (https://github.com/kubernetes/apiserver/tree/v0.20.6) and I have no issues installing act

<!-- gh-comment-id:1033630290 --> @catthehacker commented on GitHub (Feb 9, 2022): Can you show output of `go env`? That revision still exists (https://github.com/kubernetes/apiserver/tree/v0.20.6) and I have no issues installing `act`
Author
Owner

@sschuberth commented on GitHub (Feb 9, 2022):

Please see:

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/sebastian/.cache/go-build"
GOENV="/home/sebastian/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/sebastian/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/sebastian/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.13"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4134731451=/tmp/go-build -gno-record-gcc-switches"
<!-- gh-comment-id:1033649553 --> @sschuberth commented on GitHub (Feb 9, 2022): Please see: ``` $ go env GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/home/sebastian/.cache/go-build" GOENV="/home/sebastian/.config/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE="" GOMODCACHE="/home/sebastian/go/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/home/sebastian/go" GOPRIVATE="" GOPROXY="direct" GOROOT="/usr/lib/golang" GOSUMDB="off" GOTMPDIR="" GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64" GOVCS="" GOVERSION="go1.16.13" GCCGO="gccgo" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="/dev/null" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4134731451=/tmp/go-build -gno-record-gcc-switches" ```
Author
Owner

@sschuberth commented on GitHub (Feb 9, 2022):

GOMOD="/dev/null"

This looks a bit suspicious, or? Sorry, I've close to no experience with Go.

<!-- gh-comment-id:1033650336 --> @sschuberth commented on GitHub (Feb 9, 2022): > GOMOD="/dev/null" This looks a bit suspicious, or? Sorry, I've close to no experience with Go.
Author
Owner

@catthehacker commented on GitHub (Feb 9, 2022):

GOPROXY="https://proxy.golang.org,direct" GOSUMDB="sum.golang.org" go install github.com/nektos/act@latest should work

<!-- gh-comment-id:1033651616 --> @catthehacker commented on GitHub (Feb 9, 2022): `GOPROXY="https://proxy.golang.org,direct" GOSUMDB="sum.golang.org" go install github.com/nektos/act@latest` should work
Author
Owner

@catthehacker commented on GitHub (Feb 9, 2022):

Is there a reason why you won't use pre-built binaries?

<!-- gh-comment-id:1033652153 --> @catthehacker commented on GitHub (Feb 9, 2022): Is there a reason why you won't use pre-built binaries?
Author
Owner

@sschuberth commented on GitHub (Feb 9, 2022):

Is there a reason why you won't use pre-built binaries?

No, and that's what I did now as a fallback; but installing via Go seemed more natural to me as a developer.

<!-- gh-comment-id:1033654118 --> @sschuberth commented on GitHub (Feb 9, 2022): > Is there a reason why you won't use pre-built binaries? No, and that's what I did now as a fallback; but installing via Go seemed more natural to me as a developer.
Author
Owner

@sschuberth commented on GitHub (Feb 9, 2022):

GOPROXY="https://proxy.golang.org,direct" GOSUMDB="sum.golang.org" go install github.com/nektos/act@latest should work

Mind giving me a hint what this does exactly / why it's necessary in my case?

<!-- gh-comment-id:1033654493 --> @sschuberth commented on GitHub (Feb 9, 2022): > `GOPROXY="https://proxy.golang.org,direct" GOSUMDB="sum.golang.org" go install github.com/nektos/act@latest` should work Mind giving me a hint what this does exactly / why it's necessary in my case?
Author
Owner

@catthehacker commented on GitHub (Feb 9, 2022):

GOPROXY="https://proxy.golang.org,direct" GOSUMDB="sum.golang.org" go install github.com/nektos/act@latest should work

Mind giving me a hint what this does exactly / why it's necessary in my case?

Some distributions remove default GOPROXY / GOSUMDB because of privacy reasons, as Go services are hosted by Google.
GOPROXY - hosts a copy of module repositories or proxies connection in case if it's not cached
GOSUMDB - records checksums for modules and in case something changed in the source of module, it will error on mismatch

<!-- gh-comment-id:1033657546 --> @catthehacker commented on GitHub (Feb 9, 2022): > > `GOPROXY="https://proxy.golang.org,direct" GOSUMDB="sum.golang.org" go install github.com/nektos/act@latest` should work > > Mind giving me a hint what this does exactly / why it's necessary in my case? Some distributions remove default `GOPROXY` / `GOSUMDB` because of privacy reasons, as Go services are hosted by Google. `GOPROXY` - hosts a copy of module repositories or proxies connection in case if it's not cached `GOSUMDB` - records checksums for modules and in case something changed in the source of module, it will error on mismatch
Author
Owner

@sschuberth commented on GitHub (Feb 9, 2022):

Thanks. Do you think it's worth updating the official installation instructions with these settings? Or is this too much of an edge case?

<!-- gh-comment-id:1033658976 --> @sschuberth commented on GitHub (Feb 9, 2022): Thanks. Do you think it's worth updating the official installation instructions with these settings? Or is this too much of an edge case?
Author
Owner

@catthehacker commented on GitHub (Feb 9, 2022):

Do you think it's worth updating the official installation instructions with these settings? Or is this too much of an edge case?

Instruction is meant for people who already deal with Go or have it installed (I use it to compare behaviour between versions and when developing). I would prefer to have act packaged in Fedora and it's derivatives otherwise.

<!-- gh-comment-id:1033664631 --> @catthehacker commented on GitHub (Feb 9, 2022): > Do you think it's worth updating the official installation instructions with these settings? Or is this too much of an edge case? Instruction is meant for people who already deal with Go or have it installed (I use it to compare behaviour between versions and when developing). I would prefer to have `act` packaged in Fedora and it's derivatives otherwise.
Author
Owner

@catthehacker commented on GitHub (Feb 9, 2022):

https://copr.fedorainfracloud.org/coprs/goncalossilva/act/

<!-- gh-comment-id:1033665582 --> @catthehacker commented on GitHub (Feb 9, 2022): https://copr.fedorainfracloud.org/coprs/goncalossilva/act/
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#580
No description provided.