All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Bach <pascal.bach@siemens.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: anyone using docker for OE builds?
Date: Fri, 15 Apr 2016 09:18:42 +0200	[thread overview]
Message-ID: <571095D2.6020501@siemens.com> (raw)
In-Reply-To: <CAOd_LFyF5A_Xp5SGVM7cQXU=w3zhPeWsWVohb2V9VDVxMLwoTA@mail.gmail.com>

Hi Cliff

On 15.04.2016 03:44, Cliff Brake wrote:
> Hi,
>
> I've been using systemd-nspawn containers for OE builds for some
> years, and lately have been investigating Docker.  Seems like useful
> tool, but a little concerned about managing 35GB build trees in Docker
> (I already ran my workstation out of disk space once).
>
> Does anyone have any suggestions or tips for using Docker to host OE
> builds -- especially the storage aspect?
>
>
We are using docker to build several OE based products in conjunction with GitLab CI.
The only special thing we do at the moment it that we mount the sstate and download folder as a volume into the container.
This we do mostly to save some time.

But of course you need enough space in your docker runtime directory to store the docker containers while the builds are running. After that we (actually gitlab ci) usually delete the containers and the space gets freed again.

Pascal


  reply	other threads:[~2016-04-15  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  1:44 anyone using docker for OE builds? Cliff Brake
2016-04-15  7:18 ` Pascal Bach [this message]
2016-04-15 15:21 ` Otavio Salvador
2016-04-15 15:23   ` Otavio Salvador
2016-04-21 19:09     ` Cliff Brake
2016-04-22 18:14       ` Nicolas Dechesne

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=571095D2.6020501@siemens.com \
    --to=pascal.bach@siemens.com \
    --cc=openembedded-devel@lists.openembedded.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.