Re: [MirageOS-devel] experimental docker 'trusted build' of mirage

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

I believe it just means that the Docker servers do the build for
you, instead of just blindly trusting a binary image.

The trust doesn't seem to be a particularly good guarantee, since
the build scripts could potentially do anything they like.

-anil

> On 11 Nov 2014, at 11:27, Nik Sultana <ns441@xxxxxxxxx> wrote:
> 
> Sorry i probably missed some context from earlier in the thread, but in what 
> sense is the build trusted?
> (I'm wondering if it's related to a different thread in which djs55 mentioned 
> building trusted images via packer)
> Thanks,
> Nik
> 
> On 2014-11-11 11:23, Thomas Leonard wrote:
>> On 15 May 2014 20:03, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
>>> If anyone's messing around Docker, let me know if this :
>>> https://index.docker.io/u/avsm/mirage/
>>> 'trusted build' is of any use to you...
>> Seems to be broken:
>> $ docker run -it avsm/mirage
>> [ERROR] Missing parameter. Usage: 'opam config exec "<CMD> <ARG1> ... 
>> <ARGn>"'
>> 'opam config exec' failed.
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel