You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to create an arm64 rootfs on an amd64 host? currently I'm trying to build inside a docker container but I'm having a bit of trouble with that.
To avoid the XY problem, my ultimate goal is to create a root filesystem for another device (a nvidia jetson nano, it doesn't boot traditionally and so I can't install alpine normally) that it will eventually boot from. Kernel and initrd generation are handled elsewhere, so no need to worry about that, but the rootfs nvidia provides is ~10G and I'd like to use alpine instead, only problem right now is generating a rootfs for the other device to boot from.
The text was updated successfully, but these errors were encountered:
Any updates on this issue or #19? I'm trying to make a minimal rootfs for the pinebook pro. Currently only postmarketOS publishes SD card images for the PBP. I'd like to build a custom linux kernel with no initramfs (i.e. all modules and firmware built into the kernel binary) and use it along with a minimal rootfs on the SD card.
Nothing I've heard, we ultimately went with an arm docker container running in qemu-user for a while before deciding debian suited our needs better anyway.
Is it possible to create an arm64 rootfs on an amd64 host? currently I'm trying to build inside a docker container but I'm having a bit of trouble with that.
To avoid the XY problem, my ultimate goal is to create a root filesystem for another device (a nvidia jetson nano, it doesn't boot traditionally and so I can't install alpine normally) that it will eventually boot from. Kernel and initrd generation are handled elsewhere, so no need to worry about that, but the rootfs nvidia provides is ~10G and I'd like to use alpine instead, only problem right now is generating a rootfs for the other device to boot from.
The text was updated successfully, but these errors were encountered: