From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/dockerfile: add directives to run as non-root
Date: Sun, 14 Jan 2018 14:02:16 +0100 [thread overview]
Message-ID: <20180114140216.5332b2fa@windsurf> (raw)
In-Reply-To: <20180113112843.GF3226@scaer>
Hello,
On Sat, 13 Jan 2018 12:28:43 +0100, Yann E. MORIN wrote:
> On 2018-01-12 22:54 +0100, Thomas Petazzoni spake thusly:
> > On Sat, 6 Jan 2018 16:28:33 +0100, Yann E. MORIN wrote:
> > > Currently, our jobs on the gitlab-ci infra are running as root, which is
> > > problematic for two reasons:
> > >
> > > - this is not the usual way Buildroot is built;
> > > - it may miss issues where running as non-root is problematic.
> > >
> > > So, complement our Dockerfile with directives to add a new user and run
> > > everything as that user, as demonstrated by this build job:
> > > https://gitlab.com/ymorin/buildroot-ci/-/jobs/46929562
> > >
> > > Additional, enforce an UTF-8 locale while running.
> > >
> > > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > > Cc: Arnout Vandecappelle <arnout@mind.be>
> > > Cc: Peter Korsgaard <peter@korsgaard.com>
> > > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > > ---
> > > support/docker/Dockerfile | 7 +++++++
> > > 1 file changed, 7 insertions(+)
> >
> > Applied to master, thanks. Could you update the official Buildroot
> > Docker image, so that the Gitlab CI testing benefits from this ?
>
> I would if I could, but I am not supposed to have push-access to that
> image, have I?
I am not sure how that works. Hopefully Arnout can give some details
about this :)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-14 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 15:28 [Buildroot] [PATCH] support/dockerfile: add directives to run as non-root Yann E. MORIN
2018-01-12 21:54 ` Thomas Petazzoni
2018-01-13 11:28 ` Yann E. MORIN
2018-01-14 13:02 ` Thomas Petazzoni [this message]
2018-01-14 21:32 ` Arnout Vandecappelle
2018-02-03 21:47 ` Peter Korsgaard
2018-02-04 10:04 ` Yann E. MORIN
2018-02-04 14:46 ` Yann E. MORIN
2018-02-05 3:52 ` Cam Hutchison
2018-02-05 7:18 ` Yann E. MORIN
2018-02-05 9:51 ` Cam Hutchison
2018-02-05 10:56 ` Peter Korsgaard
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=20180114140216.5332b2fa@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox