From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id A5EE17D667 for ; Thu, 25 Jul 2019 01:30:27 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id x6P1UQVk028682 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 24 Jul 2019 18:30:26 -0700 (PDT) Received: from [128.224.162.148] (128.224.162.148) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.468.0; Wed, 24 Jul 2019 18:30:25 -0700 To: Bruce Ashfield References: <20190724023833.13718-1-Qi.Chen@windriver.com> <8e654160-bb32-59dc-0c35-1bcdfc3da2a3@windriver.com> From: ChenQi Message-ID: <9e2442f9-c3e1-057a-1710-1c3f4f0a0c73@windriver.com> Date: Thu, 25 Jul 2019 09:43:23 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [128.224.162.148] Cc: OE-core Subject: Re: [PATCH] container-image-busybox: add a reference container image X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2019 01:30:27 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit On 07/24/2019 08:27 PM, Bruce Ashfield wrote: > On Wed, Jul 24, 2019 at 6:00 AM ChenQi wrote: >> On 07/24/2019 05:38 PM, Burton, Ross wrote: >>> Are you aware of container-test-image.bb? Curious what the point of this is. >>> >>> Ross >> Yes. It exists in meta-selftest, having an empty /usr/bin/theapp, for >> the purpose of selftest. >> >> I think we could have some reference image for container. So I added >> this small reference image, from which users could create container and >> use shell. >> > And you do realize that such references already exist in several other > layers ? So it would be best to do a study of those options, talk to the > interested folks and then we can propose something to oe-core. > >> I expect it to be like busybox:glibc or busybox:musl in Docker Hub, with >> the major difference that we use symlinks to /bin/busybox.nosuid and >> /bin/busybox.suid while official ones use separate binaries. > Have a look at the ELCe presentations from 2018, this has been covered > in great detail at those events. > > We can't just drop an image into core without documentation, examples, > test cases, etc. That's what I'm talking about as points of collaboration. > > Cheers, > > Bruce Hi Bruce, Thanks for your info and advice. I'll do more investigation. Regards, Chen Qi >> Regards, >> Chen Qi >> >>> On Wed, 24 Jul 2019 at 03:39, Chen Qi wrote: >>>> Add a small busybox based container image. >>>> >>>> Signed-off-by: Chen Qi >>>> --- >>>> meta/recipes-core/images/container-image-busybox.bb | 8 ++++++++ >>>> 1 file changed, 8 insertions(+) >>>> create mode 100644 meta/recipes-core/images/container-image-busybox.bb >>>> >>>> diff --git a/meta/recipes-core/images/container-image-busybox.bb b/meta/recipes-core/images/container-image-busybox.bb >>>> new file mode 100644 >>>> index 0000000000..a4d63b0eea >>>> --- /dev/null >>>> +++ b/meta/recipes-core/images/container-image-busybox.bb >>>> @@ -0,0 +1,8 @@ >>>> +SUMMARY = "A small busybox based container image." >>>> +LICENSE = "MIT" >>>> + >>>> +IMAGE_INSTALL = "busybox" >>>> +IMAGE_LINGUAS = "" >>>> +IMAGE_FSTYPES = "container" >>>> + >>>> +inherit core-image >>>> -- >>>> 2.17.1 >>>> >>>> -- >>>> _______________________________________________ >>>> Openembedded-core mailing list >>>> Openembedded-core@lists.openembedded.org >>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core >> >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core > >