From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Kemal Rasim Sh <kshakir@qti.qualcomm.com>
Cc: ievlogie@qti.qualcomm.com, meta-virtualization@lists.yoctoproject.org
Subject: Re: [PATCH] docker-moby: preserve gids during docker exec
Date: Sun, 15 Nov 2026 20:43:44 -0800 (PST) [thread overview]
Message-ID: <6afa8a00.cbce3cee.49824.e4ef@mx.google.com> (raw)
In-Reply-To: <20261112090350.2918098-1-kshakir@qti.qualcomm.com>
On Thu, Nov 12, 2026 at 01:03, Kemal Rasim Sh wrote:
> Preserve and merge the original OCI additionalGids into the
> exec process specification so that groups assigned during
> container creation remain available to docker exec
> processes.
Thanks for the patches.
> +Upstream-Status: Submitted [https://github.com/moby/moby/pull/54104]
I'd like to see what upstream says about this before taking it, so
I'm going to wait for that PR to be reviewed.
For master, I'd rather pick it up with a SRCREV bump once it merges
than carry a patch. I'll decide on the stable branches after that.
You sent two different versions with the same subject, one for
master and one for wrynose, and a copy of each went to
openembedded-devel. When you send stable patches, put the branch in
the subject ([meta-virtualization][wrynose][PATCH]) and send them
here only, so it's clear which is which.
> (cherry picked from commit
> 5c36dadb2543835d79eb4d398cfc9da507f6ff882)
This hash has 41 characters, so it's worth checking.
Bruce
next prev parent reply other threads:[~2026-11-16 4:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 9:03 [PATCH] docker-moby: preserve gids during docker exec Kemal Rasim Sh
2026-11-16 4:43 ` Bruce Ashfield [this message]
2026-11-16 6:22 ` Kemal Rasim Sh (Consultant)
-- strict thread matches above, loose matches on Subject: below --
2026-11-12 9:01 Kemal Rasim Sh
2026-11-11 17:59 Kemal Rasim Sh
2026-11-11 17:28 Kemal Rasim Sh
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=6afa8a00.cbce3cee.49824.e4ef@mx.google.com \
--to=bruce.ashfield@gmail.com \
--cc=ievlogie@qti.qualcomm.com \
--cc=kshakir@qti.qualcomm.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.