From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id KKSMLmoctV/VGgAA0tVLHw (envelope-from ) for ; Wed, 18 Nov 2020 13:06:50 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 8PWKKmoctV/EeQAA1q6Kng (envelope-from ) for ; Wed, 18 Nov 2020 13:06:50 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C6B1B9404FF for ; Wed, 18 Nov 2020 13:06:45 +0000 (UTC) Received: from localhost ([::1]:40546 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfNAa-0004Gm-HU for larch@yhetil.org; Wed, 18 Nov 2020 08:06:44 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:57114) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfN1D-0005gv-Op for guix-devel@gnu.org; Wed, 18 Nov 2020 07:57:03 -0500 Received: from imta-35.everyone.net ([216.200.145.35]:37172 helo=imta-38.everyone.net) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfN1B-0007QU-1W for guix-devel@gnu.org; Wed, 18 Nov 2020 07:57:03 -0500 Received: from pps.filterd (omta001.sj2.proofpoint.com [127.0.0.1]) by imta-38.everyone.net (8.16.0.43/8.16.0.43) with SMTP id 0AICg4t5019192; Wed, 18 Nov 2020 04:56:47 -0800 X-Eon-Originating-Account: KbSKtRG2FV97hDZAFmOy1ahM0lqH3uiLvd8KgJpUblU X-Eon-Dm: m0117124.ppops.net Received: by m0117124.mta.everyone.net (EON-AUTHRELAY2 - 5a81d108) id m0117124.5f8a0284.5f035f; Wed, 18 Nov 2020 04:56:45 -0800 X-Eon-Sig: AQMHrIJftRoN96Wu6QIAAAAD,44f6b0e42347f0c4579029f7d83d7dfc X-Eip: EP5HCi1xy4WsORzar37KRatB_9EYlO75nj3MCNNp9nQ Date: Wed, 18 Nov 2020 13:56:36 +0100 From: Bengt Richter To: Danny Milosavljevic Subject: Re: Releasing guix binary in Docker format too? Message-ID: <20201118125636.GA3085@LionPure> References: <87mu0g7xiu.fsf@gnu.org> <87eelr37rn.fsf@gnu.org> <20201104154316.548b26e3@scratchpost.org> <87imai24cb.fsf@gnu.org> <86a6vufy9l.fsf@gmail.com> <20201106142801.30278d85@scratchpost.org> <86pn4esca3.fsf@gmail.com> <20201117173809.614ca823@scratchpost.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20201117173809.614ca823@scratchpost.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.312, 18.0.737 definitions=2020-11-18_04:2020-11-17, 2020-11-18 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 bulkscore=0 spamscore=0 priorityscore=1501 clxscore=1034 mlxlogscore=999 mlxscore=0 lowpriorityscore=0 adultscore=0 impostorscore=0 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2011180089 Received-SPF: pass client-ip=216.200.145.35; envelope-from=bokr@oz.net; helo=imta-38.everyone.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/18 07:56:50 X-ACL-Warn: Detected OS = Linux 3.x [generic] [fuzzy] X-Spam_score_int: -22 X-Spam_score: -2.3 X-Spam_bar: -- X-Spam_report: (-2.3 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bengt Richter Cc: Guix Devel Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: 0.49 X-TUID: Fic8v4U16VCW Hi, On +2020-11-17 17:38:09 +0100, Danny Milosavljevic wrote: > Hi, > > On Sun, 15 Nov 2020 19:30:44 +0100 > zimoun wrote: > > > $ docker exec guix guix pack hello > > user with UID 0 not found > > Docker needs to generate a /etc/passwd with uid 0 and the guix build user accounts, and a /etc/group with the guixbuild group; and whatever other users the things that are composed together using docker compose[1] require. How does this work in Docker-land ? > How much would change if the guix daemon were implemented a little differently? E.g., (quoted from [1]), does the following mean that the guix daemon potentially could run "projects" instead of guixbuilder* to create "Multiple isolated environments on a single host" ? Is it suggestive to anyone else? --8<---------------cut here---------------start------------->8--- The features of Compose that make it effective are: Multiple isolated environments on a single host Preserve volume data when containers are created Only recreate containers that have changed Variables and moving a composition between environments Multiple isolated environments on a single host Compose uses a project name to isolate environments from each other. You can make use of this project name in several different contexts: on a dev host, to create multiple copies of a single environment, such as when you want to run a stable copy for each feature branch of a project on a CI server, to keep builds from interfering with each other, you can set the project name to a unique build number on a shared host or dev host, to prevent different projects, which may use the same service names, from interfering with each other The default project name is the basename of the project directory. You can set a custom project name by using the -p command line option or the COMPOSE_PROJECT_NAME environment variable. --8<---------------cut here---------------end--------------->8--- [...] > > The question is: since Docker supports composition[1], how do they handle this standard case ? How can we get Docker to generate /etc/services, /etc/passwd and /etc/group for the composed docker image ? > I guess this question would morph if guixbuilder* became "projects", where "you can set the project name to a unique build number". [...] > > [1] https://docs.docker.com/compose/ -- Regards, Bengt Richter