All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konrad Weihmann" <kweihmann@outlook.com>
To: Ajam Ali <ajama@hcl.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Fw: Reducing rootfs size in yocto
Date: Sat, 28 Mar 2020 15:08:21 +0100	[thread overview]
Message-ID: <VI1PR05MB4286DCEF29A234000881D0F9A8CD0@VI1PR05MB4286.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <HK0PR04MB291491325C57709CD3461BB9B4CD0@HK0PR04MB2914.apcprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2985 bytes --]

Pretty general questions, but I try to answer your question.


I don't know what the purpose of your image is, but installing 
development tools like boost-dev or gcc (I guess that is what you mean 
with cpp) makes your image automatically a lot bigger, I would suggest 
to put devtools into a SDK, which could be shipped separately.


Next thing you can do is to analyze the what is actually so big in your 
image, e.g. by creating a tar.gz of the image, unpacking it and browsing 
by 'du -sh *'.
You can get the package/recipe to a file by using 'oe-pkgdata-util 
find-path <path>'.


In the identified recipe you can look for PACKAGECONFIG or OE_EXTRACONF 
switches that you don't need and disable them.


As said, I don't know what the purpose/environment of your image will be 
like, but you could also consider to use a different fs-format like squash.


In general if you want small images preferring musl over glibc and 
systemV over systemd is something that you could consider as well.


TL;DR


1) move to SDK

2) check PACKAGECONFIG switches

3) same as 2 or consider something "smaller" like lxc

4) same as 2

5) same as 2

6) same as 2

7) move to SDK

8) same as 2


On 28.03.20 14:25, Ajam Ali wrote:
>
>
> ------------------------------------------------------------------------
> Hi All,
>
> I am trying to reduce the image size.
>
> how can i reduce the size of following packages so that i could get a 
> small image size after integrating these packages in yocto?
>
>
> 1) boost-dev 2) docker 3) containerd-opencontainers 4) nodejs 5) 
> nodejs-npm 6) python3-numpy 7) cpp 8) postgresql
>
>
>
> Thanks in advance,
>
> Ajam Ali
>
>
> ::DISCLAIMER::
> ------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be 
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
> may contain viruses in transmission. The e mail and its contents (with 
> or without referred errors) shall therefore not attach any liability 
> on the originator or HCL or its affiliates. Views or opinions, if any, 
> presented in this email are solely those of the author and may not 
> necessarily reflect the views or opinions of HCL or its affiliates. 
> Any form of reproduction, dissemination, copying, disclosure, 
> modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL 
> is strictly prohibited. If you have received this email in error 
> please delete it and notify the sender immediately. Before opening any 
> email and/or attachments, please check them for viruses and other defects.
> ------------------------------------------------------------------------
>
> 

[-- Attachment #2: Type: text/html, Size: 6086 bytes --]

  reply	other threads:[~2020-03-28 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <HK0PR04MB29144DAFD598E96154278145B4CD0@HK0PR04MB2914.apcprd04.prod.outlook.com>
2020-03-28 13:25 ` Fw: Reducing rootfs size in yocto ajama
2020-03-28 14:08   ` Konrad Weihmann [this message]
2020-03-28 18:36     ` [yocto] " Ajam Ali
2020-03-28 19:45       ` Konrad Weihmann
2020-03-29 14:46   ` Oliver Westermann
2020-03-30  4:59     ` [yocto] " Ajam Ali
2020-03-30  6:57   ` Mikko Rapeli
2020-04-08 22:12     ` Randy MacLeod

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=VI1PR05MB4286DCEF29A234000881D0F9A8CD0@VI1PR05MB4286.eurprd05.prod.outlook.com \
    --to=kweihmann@outlook.com \
    --cc=ajama@hcl.com \
    --cc=yocto@lists.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.