From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6659376390151864320 X-Received: by 2002:adf:f08c:: with SMTP id n12mr1358523wro.7.1551210450307; Tue, 26 Feb 2019 11:47:30 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:f106:: with SMTP id p6ls25025wmh.6.gmail; Tue, 26 Feb 2019 11:47:29 -0800 (PST) X-Google-Smtp-Source: AHgI3Ibd+iKdkI/YlRSjOssc/xVS5Z3uQTrb8/0WbgyFu4KsmfP0JiJsBTmAqfH51kQbI1igox0r X-Received: by 2002:a1c:7dce:: with SMTP id y197mr435865wmc.16.1551210449793; Tue, 26 Feb 2019 11:47:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551210449; cv=none; d=google.com; s=arc-20160816; b=rr0rctHRwoL3tQgb6gIsL/9bdIi+hlnHi8n0tMpLtjXI/gNEelkH2/HX1YooW+uZo2 irfEpA+qu6cBfuXbURy0RRlfciujxccUzRjWulI61h5k97fA7awuoN7ghUqoOGLVvyXO miPV/sEoH/QEaaF0E7ZIyvhd4LFtyk5f6Dzzm7lJWBtkh72efA40Dolc3hp7MSsKFm/x tWnwRWbGo1Vp7bGK6MYGAx3nkC/kuckg51tHZR0iuxxUzdsR5mDoCruemmK1LQaiMVtG Df1uE7Yg8RD1ilplZl60yu9PIgNoB8kk74Cx4qO+5/SqW8JVgYc+M9WJ0ziZGL1UQRWv BrnA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:references:cc:to:from:subject; bh=xVx+vVJyvedExQb0VWdrxzd/gLZtTUAhq5CB1Iiw1RA=; b=GzrCQJH2dnAGXWcqvWS32BdbHPllOjngGucW62Cx7ZMecwb37EudD/WjN9sTsRTOAr TlQMYTxeLhOq7uwTc/EqHDEQxYYFcghL51GmQaPrFxzgeF/LRPLGeYkofQsVNjy0+cdF u6CJt8LyQv5UVWoVSDCovUGsVKusdohDjTlfMIHJEBHU4xj6ZaTBgE6nudmq2UkS/eRD OoZLZL7KDIh9Y2p3RHL8cUbPSTgViPWTIV8Y1uS2yc6xrrO/nTXLlhClC3/UNvezKKZI zxzjj/FBUxhr6q09hq0QG1gCQ221aEJhc6BoUUNX3+scI49Lqy+ARqCv5pGi4cUszKam bB/A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id r15si755wmc.4.2019.02.26.11.47.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Feb 2019 11:47:29 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id x1QJlROm031749 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 26 Feb 2019 20:47:28 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x1QJlPw1028936; Tue, 26 Feb 2019 20:47:25 +0100 Subject: Re: [PATCH] added 'isar-cfg-userpw' package From: Jan Kiszka To: "[ext] Henning Schild" , "[ext] Adler, Michael" Cc: "isar-users@googlegroups.com" , "claudius.heine.ext@siemens.com" , Claudius Heine References: <20190218162113.8538-1-claudius.heine.ext@siemens.com> <20190225101852.6m6uqbaq24upaovp@demogorgon> <20190225113406.373e0ae9@md1za8fc.ad001.siemens.net> <1577ed53-0452-9b44-d107-ad13f7240e37@siemens.com> Message-ID: Date: Tue, 26 Feb 2019 20:47:25 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <1577ed53-0452-9b44-d107-ad13f7240e37@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: 0yoYaAzNbflH On 26.02.19 20:36, [ext] Jan Kiszka wrote: > 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... No, the bug is really in common.sh, the container is fine: That script checks for group names, which is probably pointless. In this case, we are in the right group, that group just has an alias called "builder", but was originally called "users". Why the heck should we check the group? Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux