Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The docker image doesn't work with theApple M1 chip #182

Open
Chaklader opened this issue Dec 5, 2021 · 11 comments
Open

The docker image doesn't work with theApple M1 chip #182

Chaklader opened this issue Dec 5, 2021 · 11 comments

Comments

@Chaklader
Copy link

When I try to run the docker image in the Apple M1 chip computer, it always shows that port 2181 is blocked. I had to modify the Dockerfile to solve the issue temporarily, but, please, provide an official solution for the problem.

@luongnv-se
Copy link

I think Docker have Docker for M1 chip (apple chip). You can find Docker version for Apple Chip as below

@senwangJC
Copy link

When I try to run the docker image in the Apple M1 chip computer, it always shows that port 2181 is blocked. I had to modify the Dockerfile to solve the issue temporarily, but, please, provide an official solution for the problem.

Please tell me how did you get away with it, I'm having the same issue.

@senwangJC
Copy link

senwangJC commented Jan 13, 2022

I think Docker have Docker for M1 chip (apple chip). You can find Docker version for Apple Chip as below

I installed the apple silicon version for it, it does no help.

runtime.systemstack_switch() /usr/lib/go/src/runtime/asm_amd64.s:252 fp=0xc42002a768 sp=0xc42002a760

I think the golang there is just not happy.

@Chaklader
Copy link
Author

Chaklader commented Jan 13, 2022 via email

@FilipeNavas
Copy link

I was looking for a solution, and after trying a few things was able to come up with an alternative. It is a docker-compose made up of differente services and it also provides a GUI to manage your cluster. It worked on M1.

Check it out here: https://github.com/FilipeNavas/kafka-local

@Chaklader
Copy link
Author

Chaklader commented Jan 21, 2022 via email

@vikrampunchh
Copy link

    image: landoop/fast-data-dev:latest
    restart: unless-stopped
    container_name: kafka
    ports:
      - '3030:3030'
      - '8081-8083:8081-8083'
      - '9581-9585:9581-9585'
      - '9092:9092'
    environment:
      ADV_HOST: '127.0.0.1'```

getting error on docker-compose  up (M1 chip):

Broker config found at '/var/run/broker/server.properties'. We won't process variables.
kafka  | Connect worker config found at '/var/run/connect/connect-avro-distributed.properties'. We won't process variables.
kafka  | Schema registry config found at '/var/run/schema-registry/schema-registry.properties'. We won't process variables.
kafka  | REST Proxy config found at '/var/run/rest-proxy/kafka-rest.properties'. We won't process variables.
kafka  | Zookeeper config found at '/var/run/zookeeper/zookeeper.properties'. We won't process variables.
kafka  | runtime: failed to create new OS thread (have 2 already; errno=22)
kafka  | fatal error: newosproc
kafka  | 
kafka  | runtime stack:
kafka  | runtime.throw(0x512269, 0x9)
kafka  | 	/usr/lib/go/src/runtime/panic.go:566 +0x95
kafka  | runtime.newosproc(0xc420030000, 0xc42003ffc0)
kafka  | 	/usr/lib/go/src/runtime/os_linux.go:160 +0x194
kafka  | runtime.newm(0x5203a0, 0x0)
kafka  | 	/usr/lib/go/src/runtime/proc.go:1572 +0x132
kafka  | runtime.main.func1()
kafka  | 	/usr/lib/go/src/runtime/proc.go:126 +0x36
kafka  | runtime.systemstack(0x593600)
kafka  | 	/usr/lib/go/src/runtime/asm_amd64.s:298 +0x79
kafka  | runtime.mstart()
kafka  | 	/usr/lib/go/src/runtime/proc.go:1079
kafka  | 

@okazwini
Copy link

Hello,
Did anyone find a solution to this?
Thanks

@vikrampunchh
Copy link

vikrampunchh commented Feb 24, 2022

@okazwini here is the solution.

@dougdonohoe
Copy link
Contributor

Expanding on the previous comment, my #185 PR makes a multi-arch image. Try

docker pull dougdonohoe/fast-data-dev

@Tjerk-Haaye-Henricus
Copy link

Hey There,

i wonder if this PR is merged already

best regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants