From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Paulo Neves <ptsneves@gmail.com>
Cc: Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: ROOTFS_RPM_DEBUG undocumented
Date: Fri, 4 May 2018 15:41:18 +0300 [thread overview]
Message-ID: <ecb1ab50-450e-8e77-b3af-191313296602@linux.intel.com> (raw)
In-Reply-To: <CAJO0J4gz6SVhknSgPM0mGqpDR_vqsrdmNaHiXAfR4TbuxTu04Q@mail.gmail.com>
On 05/04/2018 03:42 PM, Paulo Neves wrote:
> I will propose a patch with a default bb.debug, and always have the
> verbose on dnf. Let's see how it affects the performance. I cannot
> test this in a docker container because of the problems described
> below:
>
> In the mean time I found what was happening with my slow do_rootfs. I
> was running bitbake with RPM packaging in a docker instance. It seems
> there is a problem with RPM/dnf in bitbake where it is extremely slow
> inside a docker container (1 file per second). After changing to IPK
> packages everything went smoothly.
>
> Others have had the same problem[1]. I will later report this to
> openembedded mailing list as this effectively makes RPM unusable in a
> container. I will also provide a Dockerfile to reproduce this problem.
>
> [1] https://github.com/moby/moby/issues/23137#issuecomment-359097008
No need to report. We have already fixed this and reported upstream:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/rpm/files/0001-Revert-Set-FD_CLOEXEC-on-opened-files-before-exec-fr.patch
https://bugzilla.redhat.com/show_bug.cgi?id=1537564
Alex
next prev parent reply other threads:[~2018-05-04 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 10:42 ROOTFS_RPM_DEBUG undocumented Paulo Neves
2018-05-03 13:03 ` Alexander Kanavin
2018-05-03 13:37 ` Peter Kjellerstedt
2018-05-03 14:21 ` Alexander Kanavin
2018-05-04 12:42 ` Paulo Neves
2018-05-04 12:41 ` Alexander Kanavin [this message]
2018-05-04 12:43 ` Alexander Kanavin
2018-05-04 12:50 ` Scott Rifenbark
2018-05-04 12:45 ` Alexander Kanavin
2018-05-04 12:55 ` Paulo Neves
2018-05-07 9:03 ` Mirza Krak
2018-05-07 10:12 ` Alexander Kanavin
2018-05-08 9:33 ` Peter Kjellerstedt
2018-05-08 10:29 ` Alexander Kanavin
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=ecb1ab50-450e-8e77-b3af-191313296602@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=ptsneves@gmail.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.