From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 28 Jan 2022 12:16:09 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nDPEf-00FuJa-7d for lore@lore.pengutronix.de; Fri, 28 Jan 2022 12:16:09 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nDPEe-0001an-8T; Fri, 28 Jan 2022 12:16:08 +0100 Received: from mail.benfm.de ([2a01:238:435a:9a00:9878:863:66f:ea56] helo=h2956758.stratoserver.net) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nDPEW-0001aM-QF for ptxdist@pengutronix.de; Fri, 28 Jan 2022 12:16:01 +0100 Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benfm.de; s=2020; t=1643368560; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=OMJhZUqADwxepIybP93XKoFeomtRpoh4arH5SmgSfRo=; b=aBUKUpEStzYBrUGkmoDtwE5QPg1MbEy1Xumao7cZEGG5U1Oq/8Y8SQPyYBhr4c+cQU/gEP bwuFMQpKwhDLUbyjfpH2o8sslqCrQunXO3/dG0LVLZbj+096RkagLt80ukAxEubNNpDFk7 g+ls7jxkzVmDOZ37O0kSjofko/l17+CTbNmCmj9RHAKwB8Bon7dwbEqg3R2lXho8z4y546 0iFma156/esc3UF+thYr6CMhVUy0M/xOy+j5v2v9bPme92LlivIUVk58r9608C+h1MnW+q sz/2UkP1ZDCKfmB3WOoUI/gV3Nk/X4IecE3w2BIVNbs1cHmzug8iURmDsJJDsA== Date: Fri, 28 Jan 2022 12:15:59 +0100 MIME-Version: 1.0 Content-Language: en-US To: ptxdist@pengutronix.de References: <20220127172227.GF5951@falbala.internal.home.lespocky.de> <20220128110122.GZ11273@pengutronix.de> From: Felix Mellmann In-Reply-To: <20220128110122.GZ11273@pengutronix.de> Authentication-Results: ORIGINATING; auth=pass smtp.auth=flix@benfm.de smtp.mailfrom=flix.ptxdist@benfm.de X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] Docker rules X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false On 28.01.22 12:01, Michael Olbrich wrote: > Hi, > > On Thu, Jan 27, 2022 at 06:22:28PM +0100, Alexander Dahl wrote: >> On Thu, Jan 27, 2022 at 05:37:01PM +0100, Mircea Ciocan wrote: >>> are there any official or unofficial rules to have docker container support >>> build with PTXDist on aarch64 platforms >> Do you mean running Docker containers on the target? Or buildung a >> ptxdist based BSP in a Docker container? AFAIK there's neither one or >> the other. > I don't know of any either. > > The most important questions here is, what exactly do you want to achieve? > > In my experience, Docker is mostly a buzzword that comes from the > management with the hope that everything will be magically better > afterwards. Without a clear understanding what problem should be solved. Full acknowledge! > > So I would recommend that you look take a look at you problem and verify if > Docker or any other container manager is actually what you need. > > I'm sure there are real use-cases out there where Docker is the right tool, > but I've yet to come in touch in one for PTXdist. > There is a reason why there are no Docker rules in PTXdist so far :-). I think the other way round is a more common usecase - having Dockerfiles along with the PTXdist tarball which could be used to set up working environments out of PTXdist and the latest OSELAS toolchain. Every 2 years whenever there is a new Ubuntu LTS I need to set up a Dockerfile to maintain older releases, especially when the used PTXdist and OSELAS toolchain would not build anymore on the newer Ubuntu. If someone is interested I could share my commonly used Dockerfile for this usecase. > > Regards. > Michael > _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de