Docker build fails on "make bor" for bor:v1.3.7

[klestrong]

I'm trying to build bor:v1.3.7 using Docker command docker build --tag bor:v1.3.7 . but the build keeps failing with the below error. Is it possible bor:v1.3.7 was developed using a different golang image than "latest" specified in Dockerfile? I've also included my application versions below.

141.1 # command-line-arguments
141.1 link: github.com/fjl/memsize: invalid reference to runtime.stopTheWorld
141.5 make: *** [Makefile:28: bor] Error 1
------
Dockerfile:19
--------------------
  17 |     WORKDIR ${BOR_DIR}
  18 |     COPY . .
  19 | >>> RUN make bor
  20 |
  21 |     RUN cp build/bin/bor /usr/bin/
--------------------
ERROR: failed to solve: process "/bin/sh -c make bor" did not complete successfully: exit code: 2

ubuntu@myserver:~/bor-v1.3.7$ docker version

Client: Docker Engine - Community
 Version:           25.0.2
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        29cf629
 Built:             Thu Feb  1 00:23:03 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          25.0.2
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       fce6e0c
  Built:            Thu Feb  1 00:23:03 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

ubuntu@myserver:~/bor-v1.3.7$ lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 23.04
Release:        23.04
Codename:       lunar

[klestrong]

This ticket has been resolved in the below ticket. Specifying Go 1.22 in the Dockerfile allowed the build to complete.

#1307 (comment)

[marcello33]

We applied the same patch from go-ethereum here
It will be eventually merged and released with the next release.
In the meantime, you can apply the workaround by changing the version in the Dockerfile.
Thank you.