From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Docker rules
Date: Thu, 27 Jan 2022 18:22:28 +0100 [thread overview]
Message-ID: <20220127172227.GF5951@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <c2b84555-fd52-c861-7985-16e400aa7bcd@ppc-ag.de>
[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]
Hello Mircea,
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.
> or I have to painfully dissect the
> Yocto's virtualization layer ?
If you're looking for inspiration for Docker on the target, you might
as well checkout the buildroot project [1]. That is more or less
similar to ptxdist conceptually, and IIRC it has support for Docker on
the target. Look out for package/docker* in their tree.
Greets
Alex
[1] https://www.buildroot.org/
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2022-01-27 17:23 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 [this message]
2022-01-28 11:01 ` Michael Olbrich
2022-01-28 11:15 ` Felix Mellmann
2022-01-28 11:15 ` Felix Mellmann
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=20220127172227.GF5951@falbala.internal.home.lespocky.de \
--to=post@lespocky.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