Container Tests Fail on MacOS Monterey

[dbrian]

🐞 bug report

Affected Rule

container_test()

Is this a regression?

No.

Description

Version 1.9.1 of the container-structure-test-darwin-amd64 binary is not compatible with MacOS Monterey. This is due to MacOS12BSDThreadRegisterIssue.

🔬 Minimal Reproduction

Any invocation of container_test() on MacOS Monterey will result in a similar error.

🔥 Exception or Error

+ ../structure_test_darwin/file/downloaded version
fatal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x15e1aff, 0x21)
	/usr/local/go/src/runtime/panic.go:605 +0x95 fp=0x7ff7bfefec40 sp=0x7ff7bfefec20 pc=0x102a1b5
runtime.goenvs()
	/usr/local/go/src/runtime/os_darwin.go:108 +0x83 fp=0x7ff7bfefec70 sp=0x7ff7bfefec40 pc=0x1027a53
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:492 +0xa4 fp=0x7ff7bfefecb0 sp=0x7ff7bfefec70 pc=0x102cb94
runtime.rt0_go(0x7ff7bfefece0, 0x2, 0x7ff7bfefece0, 0x1000000, 0x2, 0x7ff7bfefee88, 0x7ff7bfefeeb1, 0x0, 0x7ff7bfefeeb9, 0x7ff7bfefef6c, ...)
	/usr/local/go/src/runtime/asm_amd64.s:175 +0x1eb fp=0x7ff7bfefecb8 sp=0x7ff7bfefecb0 pc=0x105452b

🌍 Your Environment

Operating System:

  
❯ sw_vers
ProductName:	macOS
ProductVersion:	12.2
BuildVersion:	21D49
  

Output of bazel version:

  
❯ bazel version
Bazelisk version: development
Build label: 4.2.2
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Dec 2 18:28:52 2021 (1638469732)
Build timestamp: 1638469732
Build timestamp as int: 1638469732
  

Rules_docker version:

  
I'm still on v.0.17 but v0.23.0 seems to also be affected.
  

Anything else relevant?
Container structure test v1.11.0 addresses this issue.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!

[github-actions]

This issue was automatically closed because it went 30 days without a reply since it was labeled "Can Close?"