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

Unable to setup on mac m1 #765

Open
vincent0426 opened this issue May 28, 2023 · 7 comments
Open

Unable to setup on mac m1 #765

vincent0426 opened this issue May 28, 2023 · 7 comments

Comments

@vincent0426
Copy link

After running helm install owdev openwhisk/openwhisk -n openwhisk --create-namespace -f mycluster.yaml, I checked the logs of pod owdev-zookeeper-0 and received the zookeeper image error.

Failed to pull image "zookeeper:3.4": rpc error: code = Unknown desc = no matching manifest for linux/arm64/v8 in the manifest list entries

@dgrove-oss
Copy link
Member

The chart needs to be updated to use newer versions of zookeeper (and Kafka) that provide arm64 images. For zookeeper, it should be a straightforward change to using zookeeper:3.8. For Kafka, it is more involved since we need to change from wurstmeister/kafka to a different image like bitnami/kafka -- which will require some changes to the chart itself as the way that image is configured is different.

@valebes
Copy link

valebes commented Nov 22, 2023

It seems that wurstmeister/kafka is not maintained anymore (see wurstmeister/kafka-docker#742).

@vincent0426
Copy link
Author

any possible setup solution?

@OneCricketeer
Copy link

Use Strimzi if you want to run Kafka in Kubernetes

@mattvonrocketstein
Copy link

mattvonrocketstein commented May 7, 2024

It took me a long time to figure out the problem and to finally find this issue. If the problem is not fixed for 6 months, the charts in master should at least be moved to a dev branch or something. Are there other charts/values we should be looking at? If there's no current work-around then doesn't that affect production for lots of people?

@ysiivan
Copy link

ysiivan commented Jul 23, 2024

It took me a long time to figure out the problem and to finally find this issue. If the problem is not fixed for 6 months, the charts in master should at least be moved to a dev branch or something. Are there other charts/values we should be looking at? If there's no currently work-around then doesn't that affect production for lots of people?

I doubt that there are lots of people using it. It doesn't seem like it has been actively maintained. IBM is dropping OpenWhisk as well.

@dgrove-oss
Copy link
Member

See #781 and apache/openwhisk#5503.

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

6 participants