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
Issue or Feature Request:
I am trying to build bottlerocket with cargo make, but got below mlock issue. This issue got fixed (or mitigated in go 1.14.1) golang/go#37436.
[cargo-make] INFO - cargo make 0.29.0
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: default
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: empty
[cargo-make] INFO - Running Task: setup
[cargo-make] INFO - Running Task: fetch-sdk
[cargo-make] INFO - Running Task: fetch-sources
[cargo-make] INFO - Running Task: fetch-vendored
runtime: mlock of signal stack failed: 12
runtime: increase the mlock limit (ulimit -l) or
runtime: update your kernel to 5.3.15+, 5.4.2+, or 5.5+
fatal error: mlock failed
runtime stack:
runtime.throw(0xa3b43e, 0xc)
/usr/libexec/go/src/runtime/panic.go:1112 +0x72
runtime.mlockGsignal(0xc000402900)
/usr/libexec/go/src/runtime/os_linux_x86.go:72 +0x107
runtime.mpreinit(0xc000400380)
/usr/libexec/go/src/runtime/os_linux.go:341 +0x78
runtime.mcommoninit(0xc000400380)
/usr/libexec/go/src/runtime/proc.go:630 +0x108
runtime.allocm(0xc00003b000, 0x0, 0x43f200)
/usr/libexec/go/src/runtime/proc.go:1390 +0x14e
runtime.newm(0x0, 0xc00003b000)
/usr/libexec/go/src/runtime/proc.go:1704 +0x39
runtime.startm(0xc00003b000, 0xc000300000)
/usr/libexec/go/src/runtime/proc.go:1869 +0x12a
runtime.handoffp(0xc00003b000)
/usr/libexec/go/src/runtime/proc.go:1896 +0x52
runtime.entersyscallblock_handoff()
/usr/libexec/go/src/runtime/proc.go:3059 +0x30
runtime.systemstack(0x7efbb4000020)
/usr/libexec/go/src/runtime/asm_amd64.s:370 +0x66
runtime.mstart()
/usr/libexec/go/src/runtime/proc.go:1041
The text was updated successfully, but these errors were encountered:
Issue or Feature Request:
I am trying to build
bottlerocket
withcargo make
, but got below mlock issue. This issue got fixed (or mitigated in go 1.14.1) golang/go#37436.The text was updated successfully, but these errors were encountered: