it's better to have skywalking arm64 docker image

[mis98zb]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion
• Bug
• [*] Requirement
• Feature or performance improvement

---

Requirement or improvement

With the arm64 support of Elasticsearch, the only thing prevents me to run skywalking in arm environments is just the lack of skywalking arm64 docker images.
May I know is there any plan about this?

thanks & best regards.

[wu-sheng]

Hi, the current committer team seems having no one working on this. If you want, you could open a pull request to add for dev or release. Once we have the docker file, we could do that in the release process.

[mis98zb]

hi, may I know where is skywalking built on? Is it built on GitHub, or some customized environment? For your information, we cross build docker images for both amd64 & arm64 using docker buildx, which needs some special settings in the build environment. So maybe skywalking also needs some changes in the build environment…

[wu-sheng]

Yes, all of our current processes are on the GitHub CI now. Because otherwise, we can't ask every committer pushing the images by theirselves and on local env.

[mis98zb]

The docker base image aop & ui used is apline version.
However, the apline version of openjdk does not support arm architecture.
Is it possible to change the base image to openjdk:11-jre?

[wu-sheng]

From tech perspective, you can, but AFAIK there are more changes are required. Such as OpenSSL is required to install.

[mis98zb]

ok.
openjdk:11-jre contains all needed packages such as openssl & bash & gnupg & ca-certificates, so I have remove all apk instructions in docker file, :P
Build succeeded in github.
Since I don't know where to push the docker image, so I did not add --push parameter for buildx command.
So as I did not test the docker image.

How should I do in the next step? Create a pull request directly?

btw, thanks for the network issue, it's so hard to submit code to github, and open the web page to check the pipeline result...

[wu-sheng]

If you want to update, there are 2 steps at least. Add one pull request to update base image, and all e2e checked.
Then whether GitHub Action provides ARM env already? If so, add that env to existing tests.