spring-cloud-dataflow
spring-cloud-dataflow copied to clipboard
Arm64 docker images for Apple M1 usage
Currently the performance of the SCDF Docker images is poor on Apple machines with an M1 ARM chip. Everything needs to be emulated, resulting in very poor performance when running a whole docker-compose stack (i.e. your own example https://raw.githubusercontent.com/spring-cloud/spring-cloud-dataflow/v2.9.1/src/docker-compose/docker-compose.yml). This seriously affects running your software locally and holding back our progress in software development. This is currently a struggle for all the developers on our team with Apple M1 machines (50%).
Please reconsider (https://github.com/spring-cloud/spring-cloud-dataflow/issues/3855) creating multi architecture builds, at least for amd64 and arm64. It's rather straightforward using the Docker buildx cli plugin (https://github.com/docker/buildx). If assistance is required I'm more than happy to provide it.
We are awaiting a resolution for the following issue before proceeding: https://github.com/paketo-buildpacks/stacks/issues/51
This maybe of use to build an arm64 base image. - https://github.com/dmikusa-pivotal/paketo-arm64 since we are using buildpacks. We can look into https://github.com/docker/buildx as a last resort should that not work out. I've assigned this to go out in the 2.10.0 release.
@corneil created M1 images using jib. will document and reference here before closing this issue.
Documentation and scripts for creating M1 containers: https://github.com/spring-cloud/spring-cloud-dataflow/tree/main/src/local
highlight this documentation on dataflow.spring.io
Closed via https://github.com/spring-cloud/spring-cloud-dataflow/commit/c63fc3559324c88c652532482e66411daaa07bc3