mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Felix Mellmann <flix.ptxdist@benfm.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Docker rules
Date: Fri, 28 Jan 2022 12:15:59 +0100	[thread overview]
Message-ID: <a462d1fd-b07e-b6a5-bc43-1c5aa3bb792e@benfm.de> (raw)
In-Reply-To: <20220128110122.GZ11273@pengutronix.de>


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


  parent reply	other threads:[~2022-01-28 11:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 16:37 Mircea Ciocan
2022-01-27 17:22 ` Alexander Dahl
2022-01-28 11:01   ` Michael Olbrich
2022-01-28 11:15     ` Felix Mellmann
2022-01-28 11:15     ` Felix Mellmann [this message]
2022-01-28 12:40     ` Christian Melki
2022-01-28 15:18   ` Mircea Ciocan
2022-03-17 16:00   ` Enrico Weigelt, metux IT consult
2022-03-18  7:36     ` Alexander Dahl

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=a462d1fd-b07e-b6a5-bc43-1c5aa3bb792e@benfm.de \
    --to=flix.ptxdist@benfm.de \
    --cc=ptxdist@pengutronix.de \
    /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