Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> binfmt_misc

https://en.wikipedia.org/wiki/Binfmt_misc

> binfmt_misc can also be combined with QEMU to execute programs for other processor architectures as if they were native binaries.[9]

QEMU supported [ARM guest] machines: https://wiki.qemu.org/Documentation/Platforms/ARM#Supported_...

Edit: from "Running and Building ARM Docker Containers on x86" (which also describes how to get CUDA working) https://www.stereolabs.com/docs/docker/building-arm-containe... :

  sudo apt-get install qemu binfmt-support qemu-user-static # Install the qemu packages
  docker run --rm --privileged multiarch/qemu-user-static --reset -p yes # Execute the registering scripts

  docker run --rm -t arm64v8/ubuntu uname -m # Test the emulation environment
https://github.com/multiarch/qemu-user-static :

> multiarch/qemu-user-static is to enable an execution of different multi-architecture containers by QEMU [1] and binfmt_misc [2]. Here are examples with Docker [3].



Why the heck isn't there just an official Android container and/or a LineageOS container?

It's not a certified device, so.

There are a number of ways to build "multi-arch docker images" e.g. for both x86 and ARM: OCI, docker build, podman build, buildx, buildah.

Containers are testable.

Here's this re: whether the official OpenWRT container should run /sbin/init in order to run procd, ubusd,: https://github.com/docker-library/official-images/pull/7975#...

AFAIU, from a termux issue thread re: repackaging everything individually, latest Android requires binaries to be installed from APKs to get the SELinux context label necessary to run?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: