All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Konrad Scherer <Konrad.Scherer@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [layerindex-web] RFC: layer index docker fixes
Date: Thu, 12 Jul 2018 08:34:43 +0200	[thread overview]
Message-ID: <46407905.10uWkAFYrq@localhost.localdomain> (raw)
In-Reply-To: <7454b0f6-57c6-5304-0108-caa804494e57@windriver.com>

Hi Konrad

On Wednesday, 11 July 2018 7:03:28 PM CEST Konrad Scherer wrote:
> I have attached a patch to reduce the layerindex-web image size further. 
> Docker image layers are like git objects and RUN commands can only hide 
> files, not remove them once they have been committed. The pip upgrade 
> caused the following 'pip install' to fail and was removed.

Right, overall you don't save any storage space with separate stages - but the 
downside of merging these is that you lose the ability to incrementally update 
the container within those stages; any time anything before changes the whole 
block will need to be re-run. Having said that we still have the separation 
between requirements.txt and everything else which is probably sufficient.

Oddly I did not see a failure from pip when I built this yesterday, but I 
guess it's probably not strictly necessary to upgrade it anyway.

I've pushed your patch to the paule/dockerfixes branch.

> I recommend docker-compose because much of the information in 
> docker/README can be captured in a compose yaml file. It handles the 
> network setup and makes managing shared volumes much simpler.

Right, we'd just need to make sure everything we now have in the README is 
covered by the compose file (everything that's practical to cover, anyway).

Cheers,
Pau;

-- 

Paul Eggleton
Intel Open Source Technology Centre




  reply	other threads:[~2018-07-12  6:35 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 [this message]
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
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=46407905.10uWkAFYrq@localhost.localdomain \
    --to=paul.eggleton@linux.intel.com \
    --cc=Konrad.Scherer@windriver.com \
    --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.