You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Honestly, it should be pretty safe to just set GOARCH unilaterally -- if you're on amd64 and explicitly set GOARCH=amd64, it doesn't do anything (since that's the default detected value for that case). 😅
(Also, setting GOHOSTARCH and GOHOSTOS explicitly like that shouldn't be necessary.)
The text was updated successfully, but these errors were encountered:
Hi! Building https://github.com/wallarm/api-firewall-docker/blob/5cd07f115f16d10095a385a73568a4e60caf278b/0.6.7/Dockerfile on
i386
(docker build --platform linux/386
) fails with/bin/sh: api-firewall: not found
.When downloading https://github.com/wallarm/api-firewall/releases/download/v0.6.7/api-firewall-386-musl.tar.gz in an amd64 container instead, I can successfully
ldd
(and run!) the binary:I'm not 100% certain I'm looking in the right place, but it seems like
api-firewall/.github/workflows/binaries.yml
Line 156 in 9a2d7f2
case
block to setGOARCH=386
asbuild-x86:
has?api-firewall/.github/workflows/binaries.yml
Lines 95 to 102 in 9a2d7f2
Honestly, it should be pretty safe to just set
GOARCH
unilaterally -- if you're onamd64
and explicitly setGOARCH=amd64
, it doesn't do anything (since that's the default detected value for that case). 😅(Also, setting
GOHOSTARCH
andGOHOSTOS
explicitly like that shouldn't be necessary.)The text was updated successfully, but these errors were encountered: