From: "Marcin Niestrój" <m.niestroj@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gitlab-runner: new package
Date: Wed, 20 May 2020 12:03:17 +0200 [thread overview]
Message-ID: <87tv0anct6.fsf@grinn-global.com> (raw)
In-Reply-To: <CAFvCimWJUZ9fpHEKawRCOWYnajY8-R--CvEzTXrYW+-E5y4AVg@mail.gmail.com>
Hi J?r?my,
J?r?my ROSEN <jeremy.rosen@smile.fr> writes:
> Hello,
>
> I am in the process of testing that and you will probably get my tested-by
> at some point..
> Two remarks in the mean time...
> * it seems from https://docs.gitlab.com/runner/configuration/init.html
> that gitlab-runner should magically create the systemd file when
> installed. Did you test that ?
I haven't. But I had a quick tour over the code that does that. What I
understood back then was that systemd service was created by
gitlab-runner runtime. As we are cross-compiling it, then there is no
possibility to create such systemd service file before assembling final
image (without compiling for the host PC as well).
> * It seems a sane common practice to run gitlab-runner with the --user
> option pointing to a dedicated user so the gitlab jobs are not run
> as root. You should probably create a user for that and activate
> that option by default
I am not 100% sure we want that by default. The use case for me for
example is to have all system priviledges, as I use gitlab-runner to
talk to /dev/tty*, /dev/sdX and /dev/sgX devices. Some of them can be
accessed by a system group, but /dev/sgX for example is only available
with CAP_SYS_ADMIN.
I understand that for some cases it is better to reduce gitlab-runner
priviledges. But I would rather leave that for a future improvement,
when such need arises.
>
> I'll test your patch some more and come back to you
>
> Regards
> Jeremy
>
--
Regards,
Marcin Niestr?j
next prev parent reply other threads:[~2020-05-20 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 13:07 [Buildroot] [PATCH] package/gitlab-runner: new package Marcin Niestroj
2020-05-16 17:44 ` Jérémy ROSEN
2020-05-20 10:03 ` Marcin Niestrój [this message]
2020-05-20 11:30 ` Jérémy ROSEN
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=87tv0anct6.fsf@grinn-global.com \
--to=m.niestroj@grinn-global.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 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.