Same issue here without solution. Hoping anyone finds one Op zondag 14 januari 2024 om 22:53:54 UTC+1 schreef Dmitry Anderson (4nd3rs0n):
> I'm having the same problem. For now I just vendor modules to a project > modules and run without installing anything from the container, but also > would like to find a fix. > On Monday, May 22, 2023 at 2:29:08 AM UTC+2 Joao Miguel Ferreira wrote: > >> Hello all, >> >> My docker build is ok with FROM golang:1.18-alpine, FROM >> golang:1.18-buster and FROM golang:1.18-bullseye images. The application >> works. All is fine on the 3 cases. >> >> But the docker build fails with FROM golang:1.20-alpine, FROM >> golang:1.20-buster and FROM golang:1.20-bullseye images. >> >> This is the error message I get: >> >> go: github.com/davecgh/go-...@v1.1.1 >> <http://github.com/davecgh/go-spew@v1.1.1>: Get " >> https://proxy.golang.org/github.com/davecgh/go-spew/@v/v1.1.1.mod": dial >> tcp [2a00:1450:4003:801::2011]:443: connect: cannot assign requested address >> >> It happens during go mod download. It happens when building on Debian11, >> Debian12 and Ubuntu22 hosts. >> >> I have tried many things including going inside the container and >> downloading the module with wget. It works fine. Maybe something changed >> from 1.18 to 1.20 related to ipv6. >> >> I would like to be able to do the build with one golang 1.20 image. But I >> can not understand what is wrong. Can you help clarify that error and how >> to overcome it? >> >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/09552ed6-0469-425d-9dcf-10fac6cde049n%40googlegroups.com.
