Philippe Mathieu-Daudé writes:
> Hi Alex,
>
> I first tried "make docker-image-debian-armhf-cross NOUSER=1 V=1"
> which worked fine, then "make docker-image-debian-armhf-cross
> NOUSER=0" but got a "Image is up to date." I thought I should have to
> remove the image manually so
Hi Alex,
I first tried "make docker-image-debian-armhf-cross NOUSER=1 V=1" which
worked fine, then "make docker-image-debian-armhf-cross NOUSER=0" but
got a "Image is up to date." I thought I should have to remove the image
manually so I typed "docker rmi qemu:debian-armhf-cross" and tried
On Thu, 02/16 12:34, Alex Bennée wrote:
> Currently all docker builds are done by exporting a tarball to the
> docker container and running the build as the containers root user.
> Other use cases are possible however and it is possible to map a part
> of users file-system to the container. This
Currently all docker builds are done by exporting a tarball to the
docker container and running the build as the containers root user.
Other use cases are possible however and it is possible to map a part
of users file-system to the container. This is useful for example for
doing cross-builds of