search

lensesio / fast-data-dev

Kafka Docker for development. Kafka, Zookeeper, Schema Registry, Kafka-Connect, , 20+ connectors
https://lenses.io
Apache License 2.0
2.02k stars 333 forks source link

(M1 Big Sur) Failed to create new OS thread (have 2 already; errno=22) #176

Open sahityakumarsuman opened 3 years ago

sahityakumarsuman commented 3 years ago

I was trying to run this image locally with following command for my KAFKA, ZooKeeper setup

`docker run --rm -it -p 3181:3181 -p 3040:3040 -p 7081:7081 -p 7082:7082 -p 7083:7083 -p 7092:7092 -e ZK_PORT=3181 -e WEB_PORT=3040 -e REGISTRY_PORT=8081 -e REST_PORT=7082 -e CONNECT_PORT=7083 -e BROKER_PORT=7092 -e ADV_HOST=127.0.0.1 landoop/fast-data-dev

`

First I get the following warning

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

And following is the log that a receive entirely 

Setting advertised host to 127.0.0.1.
runtime: failed to create new OS thread (have 2 already; errno=22)
fatal error: newosproc

runtime stack:
runtime.throw(0x512269, 0x9)
    /usr/lib/go/src/runtime/panic.go:566 +0x95
runtime.newosproc(0xc420030000, 0xc42003ffc0)
    /usr/lib/go/src/runtime/os_linux.go:160 +0x194
runtime.newm(0x5203a0, 0x0)
    /usr/lib/go/src/runtime/proc.go:1572 +0x132
runtime.main.func1()
    /usr/lib/go/src/runtime/proc.go:126 +0x36
runtime.systemstack(0x593600)
    /usr/lib/go/src/runtime/asm_amd64.s:298 +0x79
runtime.mstart()
    /usr/lib/go/src/runtime/proc.go:1079

goroutine 1 [running]:
runtime.systemstack_switch()
    /usr/lib/go/src/runtime/asm_amd64.s:252 fp=0xc42002a768 sp=0xc42002a760
runtime.main()
    /usr/lib/go/src/runtime/proc.go:127 +0x6c fp=0xc42002a7c0 sp=0xc42002a768
runtime.goexit()
    /usr/lib/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc42002a7c8 sp=0xc42002a7c0
Could not successfully bind to port 3181. Maybe some other service
in your system is using it? Please free the port and try again.
Exiting.

Please let me know if anyone comes around on working fix with this given issue

ericnograles commented 3 years ago

Looks related to #175?

vilterpanitz commented 2 years ago

Hi there - Do you have plans to support arm64 / Apple M1 chips? I looked into the related issue, but it's still opened and the workaround involves cloning a forked project and building it my own. I was looking into a more "official" fix for this.