I now created Docker images uses debootstrap: sudo debootstrap --arch riscv64 --foreign resolute chroot/ http://ports.ubuntu.com/ubuntu-ports sudo chroot chroot /debootstrap/debootstrap --second-stage cat > Dockerfile_debootstrap_resolute << eof FROM scratch ADD chroot/ / CMD ["bash"] eof sudo docker build -t debootstrap_resolute -f Dockerfile_debootstrap_resolute . sudo docker run -ti debootstrap_resolute /bin/bash
rm -rf chroot/ sudo debootstrap --arch riscv64 --foreign plucky chroot/ http://ports.ubuntu.com/ubuntu-ports sudo chroot chroot /debootstrap/debootstrap --second-stage cat > Dockerfile_debootstrap_plucky << eof FROM scratch ADD chroot/ / CMD ["bash"] eof sudo docker build -t debootstrap_plucky -f Dockerfile_debootstrap_plucky . sudo docker run -ti debootstrap_plucky /bin/bash Again with Resolute no prompt. With Plucky a proper command line prompt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2133188 Title: Illegal instruction in memset under qemu-user for riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/2133188/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
