nginx-proxy: Latest update of dockergen / forego broke container ("pthread_create failed")
Latest update(s) of dockergen / forego broke the (automated build) of the container, probably due to 19f8d7e37535a4330d0cf20dfcba226502ea499f:
forego | starting dockergen.1 on port 5100
dockergen.1 | runtime/cgo: pthread_create failed: Operation not permitted
dockergen.1 | SIGABRT: abort
dockergen.1 | PC=0x7ffb2f2b1ccc m=0 sigcode=18446744073709551610
dockergen.1 |
dockergen.1 | goroutine 0 [idle]:
dockergen.1 | runtime: g 0: unknown pc 0x7ffb2f2b1ccc
dockergen.1 | stack: frame={sp:0x7ffc05d9e650, fp:0x0} stack=[0x7ffc0559fad0,0x7ffc05d9eae0)
dockergen.1 | 0x00007ffc05d9e550: 0x0000000000c4048c 0x0000000000000000
dockergen.1 | 0x00007ffc05d9e560: 0x00000000008bbf6e 0x0000000000000006
dockergen.1 | 0x00007ffc05d9e570: 0x0000000000c4048a 0x0000000000000000
dockergen.1 | 0x00007ffc05d9e580: 0x00000000008bb602 0x0000000000000004
dockergen.1 | 0x00007ffc05d9e590: 0x0000000000000000 0x0000000000000000
dockergen.1 | 0x00007ffc05d9e5a0: 0x0000000000000000 0x0000000000000000
dockergen.1 | 0x00007ffc05d9e5b0: 0x0000000000000000 0x0000000000000000
dockergen.1 | 0x00007ffc05d9e5c0: 0x0000000000000000 0x0000000000000000
Reverting the container to jwilder/nginx-proxy:1.3 fixed the problem at least temporarily for me.
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 18 (9 by maintainers)
That’s good news, it means it’s likely
cgorelated. I’ll try to push a patched version to validate the fix as soon as I have access to an x86_64 host.Thanks for fixing!
nginxproxy/nginx-proxy:latestalso works for me again.@johnvcoleman-w24 you can skip testing
nginxproxy/nginx-proxy:2268and directly pullnginxproxy/nginx-proxy:latestYes,
nginxproxy/nginx-proxy:2268is working fine for me as wellJust gave
nginxproxy/nginx-proxy:2268a quick spin, seems to work fine here now!