Maybe provide an arm64 image for local development

[Kailai-Wang]

Context

mentioned by @jonalvarezz , the current litentry-parachain image won't work for Apple Silicon.
Despite of having staging and rococo network, sometimes a local setup is more efficient.

Let's check if it's easy to compile an arm64 image -- but please don't spend too much time if we see major blockers.

See also:
open-web3-stack/parachain-launch#70 (we are using parachain-launch too)

---

✔️ Please set appropriate labels and assignees if applicable.

[Kailai-Wang]

Do we have a conclusion? Shall we icebox this issue for now?

[BillyWooo]

paritytech/polkadot-sdk#802

[github-actions]

❗ This issue is stale because it has been open for 60 days with no activity.
Remove Stale label or update it, otherwise this issue will be closed in 7 days.
@litentry/parachain

[github-actions]

🔐 This issue was closed because there has been no activity for 7 days since it became stale.

[Kailai-Wang]

Still TODO. Deprioritise it again as not in urgent need.

[bredamatt]

Being able to build images on an M1 would indeed be useful. I am working on improving tracing for the Parachain Engineering team. This is an iterative task, and I need high velocity local deployments of relay chain networks to do it. Containers are the go to for that. Yet, I am on an M1...

I have setup a local kubernetes environment which runs the entire tracing stack required, and I have successfully deployed the paritytech/node images in this environment using helm. However, because I need to build new images from my local branch the current Dockerfile's provided in the polkadot repo do not work given that I am on an M1.

[BillyWooo]

following: paritytech/polkadot#6108

[github-actions]

❗ This issue is stale because it has been open for 60 days with no activity.
Remove Stale label or update it, otherwise this issue will be closed in 7 days.
@litentry/parachain