Re: [Qemu-devel] [RISU PATCH v5 05/13] build-all-archs: support cross building via docker

["Alex Bennée" <alex.bennee@linaro.org>]

Peter Maydell <peter.maydell@linaro.org> writes:

> On 19 June 2017 at 11:46, Alex Bennée <alex.bennee@linaro.org> wrote:
>> If we want to link to any other libraries we might find using simple
>> cross toolchains doesn't work so well. One way around this is to use a
>> dockerised cross-toolchain which then won't clash with your host
>> system. If the user specifies --use-docker the obvious will be done.
>>
>> By default we use the QEMU projects qemu:debian-FOO-cross images as
>> RISU hackers are likely to be QEMU developers too. However any docker
>> tag can be passed on the command line.
>>
>> If none of the docker images have usable compilers we fall back to
>> checking the host path.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> $ ./build-all-archs --use-docker
> Got permission denied while trying to connect to the Docker daemon
> socket at unix:///var/run/docker.sock: Get
> http://%2Fvar%2Frun%2Fdocker.sock/v1.27/images/json?filters=%7B%22reference%22%3A%7B%22qemu%22%3Atrue%7D%7D:
> dial unix /var/run/docker.sock: connect: permission denied
>
> but maybe my local docker setup is just broken?

Generally you need to add yourself to the "docker" group to have access.
This isn't recommended in production but the alternative is to preface
all docker calls with sudo and set up permissions that way. The official
docs discuss it here:

  https://docs.docker.com/engine/installation/linux/linux-postinstall/

The advice that "only trusted users should be allowed to control your
Docker daemon." is valid but irrelevant to developers who generally have
complete control of their own box.

>
> thanks
> -- PMM


--
Alex Bennée