Yes, but chroot itself is not working, which is called from multistrap when 
creating a rootfs with same architecture as the host system.
I also didn't specify a setupscript and my multistrap.conf looks as follows:

[General]
noauth=false
unpack=true
bootstrap=debian-stretch
aptsources=debian-stretch

[debian-stretch]
source=http://deb.debian.org/debian
suite=stretch
components=main contrib non-free
packages=

Regards,
Benedikt

Am Donnerstag, 19. Oktober 2017 13:41:02 UTC+2 schrieb Alexander Smirnov:
>
> On 10/19/2017 02:36 PM, Benedikt Niedermayr wrote: 
> > I found the problem. 
> > 
> > When running multistrap with the host architecture (amd64), then 
> > multistrap will automatically run chroot to configure the 
> > extracted *.deb packages. 
> > This is not the case when running multistrap with a foreign architecture 
> > (armhf). 
> > 
> > Keeping in mind, that also amd64 based rootfs builds should be possible, 
> > some problems still persist. 
> > 
>
> It's not the problem, PRoot successfully works with  QEMU like chroot: 
>
> asmirnov@zbook:~/Work/isar/isar/build/tmp/work/debian-jessie-armhf/buildchroot$ 
>
> PROOT_NO_SECCOMP=1 proot -q qemu-arm -0 -r rootfs /bin/bash 
> proot warning: can't 
> chdir("/home/asmirnov/Work/isar/isar/build/tmp/work/debian-jessie-armhf/buildchroot/./.") 
>
> in the guest rootfs: No such file or directory 
> proot info: default working directory is now "/" 
> root@zbook:/# 
>
>
> > Regards, 
> > Benedikt 
>
> -- 
> With best regards, 
> Alexander Smirnov 
>
> ilbers GmbH 
> Baierbrunner Str. 28c 
> D-81379 Munich 
> +49 (89) 122 67 24-0 
> http://ilbers.de/ 
> Commercial register Munich, HRB 214197 
> General manager: Baurzhan Ismagulov 
>