From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
"[ext] Adler, Michael" <michael.adler@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"claudius.heine.ext@siemens.com" <claudius.heine.ext@siemens.com>,
Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] added 'isar-cfg-userpw' package
Date: Tue, 26 Feb 2019 20:36:57 +0100 [thread overview]
Message-ID: <1577ed53-0452-9b44-d107-ad13f7240e37@siemens.com> (raw)
In-Reply-To: <20190225113406.373e0ae9@md1za8fc.ad001.siemens.net>
On 25.02.19 11:34, [ext] Henning Schild wrote:
> Hi,
>
> this is not related to the package. But to any package that goes
> through common.sh and checks the ids.
>
> https://groups.google.com/forum/#!searchin/isar-users/Align$20UID$20and$20GID$20%7Csort:date/isar-users/S5W8D3X4Lkg/n7HbASWnAwAJ
>
> The result of this discussion was that we probably need to align the
> ids and hope we never get in trouble with the host. In this case we do!
>
> The alignment should be changed. If the group does exist (100) join the
> user and do not try and create a group. The check should be changed to
> make sure the gid is the main group gid, instead of 1000.
FWIW, just ran into the same issue after purging my build folder and retrying a
clean "kas-docker --isar build". I'm not seeing it with jailhouse-images where
we do not use kas-docker yet and also do not create the build folder outside of
the container, thus with host IDs.
So, this needs to be fixed in our kas-isar container, I suppose...
Jan
>
> Henning
>
> Am Mon, 25 Feb 2019 10:18:52 +0000
> schrieb "[ext] Adler, Michael" <michael.adler@siemens.com>:
>
>> Just a heads-up, I'm having some issues with this package:
>>
>> ==============================SNIP
>> START======================================= NOTE: Executing RunQueue
>> Tasks ERROR: mc:qemuamd64-stretch:isar-cfg-rootpw-1.0-r0 do_build:
>> Function failed: do_build (log file is located
>> at /work/build/tmp/work/debian-stretch-amd64/isar-cfg-rootpw-1.0-r0/temp/log.do_build.179)
>> ERROR: Logfile of failure stored
>> in: /work/build/tmp/work/debian-stretch-amd64/isar-cfg-rootpw-1.0-r0/temp/log.do_build.179
>> Log data follows: | DEBUG: Executing shell function do_build | This
>> script can only be run as root:root or builder:builder! | (Currently
>> running as builder(1000):users(100)) | WARNING: exit code 1 from a
>> shell command. | ERROR: Function failed: do_build (log file is
>> located
>> at /work/build/tmp/work/debian-stretch-amd64/isar-cfg-rootpw-1.0-r0/temp/log.do_build.179)
>> ERROR: Task
>> (multiconfig:qemuamd64-stretch:/work/isar/meta/recipes-support/isar-cfg-rootpw/isar-cfg-rootpw.bb:do_build)
>> failed with exit code '1' ==============================SNIP END
>> =======================================
>>
>> My setup:
>>
>> - NixOS (most notably: uid=1000, gid=100, uid != gid)
>> - Isar runs inside a Docker image (kasproject/kas-isar)
>>
>> However I could imagine that this also breaks in native mode as soon
>> as uid != gid (though I will not attempt to run Isar natively). Any
>> ideas?
>>
>> Kind regards,
>> Michael
>>
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-26 19:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 16:21 claudius.heine.ext
2019-02-18 16:58 ` Henning Schild
2019-02-19 9:19 ` Henning Schild
2019-02-23 10:42 ` Jan Kiszka
2019-02-25 8:07 ` Jan Kiszka
2019-02-25 8:44 ` Claudius Heine
2019-02-25 8:48 ` Jan Kiszka
2019-02-25 9:32 ` Henning Schild
2019-02-25 11:15 ` Jan Kiszka
2019-02-25 11:44 ` Claudius Heine
2019-03-04 10:15 ` Claudius Heine
2019-02-25 11:18 ` Claudius Heine
2019-02-25 10:18 ` Adler, Michael
2019-02-25 10:34 ` Henning Schild
2019-02-25 11:38 ` Henning Schild
2019-02-26 19:36 ` Jan Kiszka [this message]
2019-02-26 19:47 ` Jan Kiszka
2019-02-27 8:46 ` Henning Schild
2019-02-27 10:20 ` Henning Schild
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=1577ed53-0452-9b44-d107-ad13f7240e37@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=michael.adler@siemens.com \
/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