From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Michael Halstead <michael@yoctoproject.org>,
Konrad Scherer <konrad.scherer@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [layerindex-web] RFC: layer index docker fixes
Date: Thu, 06 Sep 2018 00:04:53 +1200 [thread overview]
Message-ID: <3087295.eQxHIGtfj0@localhost.localdomain> (raw)
In-Reply-To: <1924287.nmYE9jUvR3@localhost.localdomain>
On Thursday, 30 August 2018 11:44:10 AM NZST Paul Eggleton wrote:
> On Wednesday, 29 August 2018 10:46:27 PM NZST Paul Eggleton wrote:
> > I know Konrad promised to update the docker-compose setup to be closer
> > to what we'd done recently with the docker setup, but I needed something
> > urgently and wanted to learn how to use docker-compose anyway, so I've
> > put this together:
> >
> > http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/log/?h=paule/docker-compose
> >
> > Let me know what you think - it works well enough for me here, although the
> > setup commands are now a bit ugly on their own.
>
> I realised this morning that "docker-compose run" can simplify a lot of the
> docker run commands, so I've just converted most of the commands in
> docker/README and pushed the branch again.
So, any comments?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2018-09-05 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 16:17 [layerindex-web] RFC: layer index docker fixes Paul Eggleton
2018-07-11 17:03 ` Konrad Scherer
2018-07-12 6:34 ` Paul Eggleton
2018-07-12 20:16 ` Konrad Scherer
2018-07-13 7:29 ` Paul Eggleton
2018-07-16 18:24 ` Konrad Scherer
2018-07-16 20:16 ` Paul Eggleton
2018-07-17 10:16 ` Paul Eggleton
2018-07-17 14:48 ` Konrad Scherer
2018-08-29 10:46 ` Paul Eggleton
2018-08-29 23:44 ` Paul Eggleton
2018-09-05 12:04 ` Paul Eggleton [this message]
2018-10-02 18:45 ` Konrad Scherer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3087295.eQxHIGtfj0@localhost.localdomain \
--to=paul.eggleton@linux.intel.com \
--cc=konrad.scherer@windriver.com \
--cc=michael@yoctoproject.org \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.