Require images for ARM64

[odidev]

Hi Team,

I am trying to use apicurio-studio images in arm64 machine, but arm64 tag is not available for any of the images.

I have built API, UI, and WS images on the arm64 machine successfully. I have added buildx in GitHub actions but it requires the installation to be done from dockerfile to build target jars and run them.

Do you have any plans on releasing arm64 images?

If interested, I will raise a PR with buildx changes.

[EricWittmann]

We don't have any current plans to release arm64 images. I'd be very happy to see a PR with the required changes.

[odidev]

@EricWittmann,

I have added a job for releasing docker images for arm64. Please have a look

Commit Link - odidev@3b57852

GHA Logs Link - https://github.com/odidev/apicurio-studio/runs/5770938137?check_suite_focus=true

DockerHub Images Links -

• Apicurio-studio-api:- https://hub.docker.com/repository/docker/odidev/apicurio-studio-api
• Apicurio-studio-ws:- https://hub.docker.com/repository/docker/odidev/apicurio-studio-ws
• Apicurio-studio-ui:- https://hub.docker.com/repository/docker/odidev/apicurio-studio-ui

If you are fine with the above changes, I am happy to raise a PR.

[EricWittmann]

@carlesarnal any thoughts on this?

[carlesarnal]

I think this is an interesting idea. That said, I would have expected modifications to the current job to release the images for arm using buildx to build the images for both platforms instead of creating a fresh new job. @odidev please, open a PR, and we can continue the discussion there.

[EricWittmann]

@riprasad Since you did this recently for Registry, could you implement it for Studio as well? :)

[odidev]

@EricWittmann

I have successfully built ARM64 image of apicurio-studio-auth on my local ARM64 machine and, I could see that the image for amd64 is released here but there is no specific release process mentioned. If I could get the release process for images, I would add ARM64 and raise PR for the same.

[EricWittmann]

Sorry for the delay, @odidev and thank you for the offer. Right now the apicurio-studio-auth image is just released manually, because we don't release it very often.

So really we need to create a new separate GH workflow for this!

@riprasad wdyt? Easy to create a new standalone workflow for apicurio-studio-auth? I think it should initially be just manually triggered, but we can figure out an appropriate auto=trigger later.

The source for that image is here:

https://github.com/Apicurio/apicurio-studio/tree/master/distro/openshift/auth

[riprasad]

@odidev I was able to build the apicurio-studio-auth image in arm64, which is a bit surprising to me since the base image is only available for amd64. I thought it was also necessary for the base image to be available for the target platform.

[odidev]

@riprasad, As arm64 image of keycloack is not present on docker.io, we need to use the keycloak image available in quay.io.