From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Qi.Chen@windriver.com
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH] nerdctl: use -modcacherw to avoid do_rm_work failure
Date: Mon, 9 Feb 2026 20:06:56 +0000 [thread overview]
Message-ID: <aYo-YEn4nriQZ2cg@gmail.com> (raw)
In-Reply-To: <CADkTA4PmJ16DoD8sdN1XrU3ATJY_Q-MEwCZX9bpk61QY5+qoYw@mail.gmail.com>
In message: Re: [meta-virtualization][PATCH] nerdctl: use -modcacherw to avoid do_rm_work failure
on 04/02/2026 Bruce Ashfield wrote:
> On Mon, Feb 2, 2026 at 10:52 PM Chen Qi via lists.yoctoproject.org <Qi.Chen=
> windriver.com@lists.yoctoproject.org> wrote:
>
> > From: Chen Qi <Qi.Chen@windriver.com>
> >
> > When rm_work is enabled, building nerdctl fails because do_rm_work
> > fails to remove the contents under pkg/mod/ as they are readonly.
> > Use '-modcacherw' to fix this issue.
> >
>
> I'm going a different way to fix this.
>
> I've avoided using modcacherw so far, and would like to continue as
> having it on can mask some issues.
>
> I have permissions fixups, they should be firing for this, and I'm
> sorting that out now as I work through some package updates.
I moved where the permissions fixups fire, so they should now
run after do_compile (which may change the permissions).
This means we don't need per-recipe fixes, and it covers all
types of builds (directly invoked, makefiles, ones that don't
inherit our variables etc).
Bruce
>
> Bruce
>
>
> >
> > Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> > ---
> > recipes-containers/nerdctl/nerdctl_git.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/recipes-containers/nerdctl/nerdctl_git.bb
> > b/recipes-containers/nerdctl/nerdctl_git.bb
> > index 8f63b48c..1c37bcf8 100644
> > --- a/recipes-containers/nerdctl/nerdctl_git.bb
> > +++ b/recipes-containers/nerdctl/nerdctl_git.bb
> > @@ -78,7 +78,7 @@ do_compile() {
> > export CGO_LDFLAGS="${LDFLAGS} --sysroot=${STAGING_DIR_TARGET}"
> >
> > # -trimpath removes build paths from the binary (required for
> > reproducible builds)
> > - oe_runmake GO=${GO} BUILDTAGS="${BUILDTAGS}"
> > GO_BUILD_FLAGS="-trimpath" binaries
> > + oe_runmake GO=${GO} BUILDTAGS="${BUILDTAGS}"
> > GO_BUILD_FLAGS="-trimpath -modcacherw" binaries
> > }
> >
> > do_install() {
> > --
> > 2.34.1
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#9554):
> > https://lists.yoctoproject.org/g/meta-virtualization/message/9554
> > Mute This Topic: https://lists.yoctoproject.org/mt/117611093/1050810
> > Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> > Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [
> > bruce.ashfield@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
> >
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
next prev parent reply other threads:[~2026-02-09 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 3:51 [meta-virtualization][PATCH] nerdctl: use -modcacherw to avoid do_rm_work failure Qi.Chen
2026-02-05 1:38 ` Bruce Ashfield
2026-02-09 20:06 ` Bruce Ashfield [this message]
2026-02-10 2:58 ` Chen, Qi
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=aYo-YEn4nriQZ2cg@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=Qi.Chen@windriver.com \
--cc=meta-virtualization@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.