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

Functionality query #163

Open
DustyArmstrong opened this issue Feb 17, 2024 · 1 comment
Open

Functionality query #163

DustyArmstrong opened this issue Feb 17, 2024 · 1 comment

Comments

@DustyArmstrong
Copy link

I have a query around the depth of support Binfmt has, primarily around running the actual services inside the emulated containers.

I am able to spin up amd64 containers easily enough on an aarch64 ARM platform, and while the containers do run and I can drop into a shell no problem, the services of some don't seem to start (definitely not all do it). Looks like it may be related to a timeout while starting the server itself inside the container - lack of resources? The host I'm running on still seems to have plenty of CPU and memory overhead.

Can I ask whether it's normal for emulated containers to run but not run? Are there still caveats and aspects of Binfmt that don't quite emulate the full architecture whereby some components just don't or can't reliably run? Or should, if the container itself runs, the whole service inside realistically be running too? Thanks!

@DustyArmstrong
Copy link
Author

Tried to run the same container on a more powerful Pi 4, I was testing on an older unit before slinging it into (homelab) production. It does now run albeit slightly slower than native ARM, to be expected, so it must just be resources. I would still appreciate confirmation of the above, but maybe it's a stupid question.

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

1 participant