Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linux/arm64 - The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) #731

Open
Backtrennpapier opened this issue Nov 10, 2024 · 6 comments

Comments

@Backtrennpapier
Copy link

Hi,

I started to execute on a planned mail server migration over to a new setup including mailman. That setup runs on a linux/arm64 machine. It seems that there are not images for that platform available.

! mailman-core The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s
! mailman-web The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested 0.0s

The containers will be stopped, mailman can't be run. I also discovered the older issue which maybe was never solved: #483

Are there any plans on adding support for this architecture in the near future?

@Backtrennpapier Backtrennpapier changed the title linux/arm64 - linux/arm64 - The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) Nov 10, 2024
@maxking
Copy link
Owner

maxking commented Nov 19, 2024

Can you contribute arm64 version of the dockerfiles with CI code? I don't honestly know much about multi-platform dockerfiles and i'd love to keep them separate.

@Backtrennpapier
Copy link
Author

Unfortunately I'm not an expert on CI, but as much as I understand the current build process if running in a circleCI pipeline needs to be adapted to cover the multi-platform build. Maybe that is already wrong. Is there any other contributor who could support with this?

@midzelis
Copy link

midzelis commented Feb 1, 2025

See also #741

@domdorn
Copy link

domdorn commented Feb 9, 2025

Also having this problem.

I have enabled amd64 emulation using

docker run --privileged --rm tonistiigi/binfmt --install all

the mailman-core container starts, however, the mailman-web container is in a kind of crash-loop where it exits and restarts right after something with uWSGI

e.g. docker logs -f mailman-web:

File “/usr/lib/python3.12/site-packages/django/contrib/sites/locale/hu/LC_MESSAGES/django.po” is already compiled and up to date.
File “/usr/lib/python3.12/site-packages/django/contrib/sites/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date.
/opt/mailman-web
 Compressing... done
Compressed 2 block(s) from 80 template(s) for 1 context(s).
Operations to perform:
  Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, openid, postorius, sessions, sites, socialaccount
Running migrations:
  No migrations to apply.
Creating admin user domdorn ...
Superuser domdorn already exists
Setting list.xxx.com as the default domain ...
[uWSGI] getting INI configuration from /opt/mailman-web/uwsgi.ini

@Backtrennpapier
Copy link
Author

Been down the emulation route and landed in the same problem. I concluded that besides it not working it is also a very inefficient use of resources on a virtual server. Instead I migrated to an amd64 arch and mailman on that still requires some memory, which will not get better emulating it.
In the meantime maybe @midzelis provided the solution for the arm64 images.

@domdorn
Copy link

domdorn commented Feb 11, 2025

@maxking could you please review the PR of @midzelis and if acceptable, merge it and trigger a new release? Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants