Mina daemon container does not run on Mac M1

[vlad2095]

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions

Description

Basically, image doesn't support arm architecture.
I found comment in the old issue about that, looks related:
#8970 (comment)
I use podman in the examples, docker experience is the same.

Steps to Reproduce

Trying to run mina daemon within container

podman run --arch linux/amd64 --name mina-daemon \
--env MINA_PRIVKEY_PASS=My_V3ry_S3cure_Privat3K3yPassw0rd --env MINA_LIBP2P_PASS=LIBP2p_PASSWrod --env PEER_LIST_URL=https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt \
--env LOG_LEVEL=Debug --env FILE_LOG_LEVEL=Debug docker.io/minaprotocol/mina-daemon:3.0.0-93e0279-bullseye-mainnet

Output

WARNING: image platform (linux/amd64) does not match the expected platform (linux/linux/amd64)
Mina process exited with status code 1

Same trying to start with sh entrypoint

 podman run --rm --name mina-daemon --entrypoint sh docker.io/minaprotocol/mina-daemon:3.0.0-93e0279-bullseye-mainnet
Trying to pull docker.io/minaprotocol/mina-daemon:3.0.0-93e0279-bullseye-mainnet...
Getting image source signatures
Copying blob sha256:710798a36c67f50fc2b88fb80c0d543c44a71179ae436467dce5517bb0118901
...
Copying config sha256:0bc6abf5bbf727e51871197d54890b6108aef6ce0e9be18fd4fe5d1af9de71fb
Writing manifest to image destination
WARNING: image platform (linux/amd64) does not match the expected platform (linux/arm64)

Expected Result

mina daemon running inside docker container

Actual Result

WARNING: image platform (linux/amd64) does not match the expected platform (linux/linux/amd64)
Mina process exited with status code 1

Daemon version

mina-daemon:3.0.0-93e0279-bullseye-mainnet

How frequently do you see this issue?

Always

What is the impact of this issue on your ability to run a node?

Blocker

Status

exited

Additional information

No response