From mboxrd@z Thu Jan 1 00:00:00 1970 From: Esben Haabendal Date: Mon, 23 Sep 2019 09:44:36 +0200 Subject: [Buildroot] [All Systems Go!] Buildroot : Using embedded tools to build container images In-Reply-To: <87y2ygw5ql.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Sun, 22 Sep 2019 20:22:42 +0200") References: <8c2d3dbb-8f85-7f1d-c82b-65f0573a7c76@smile.fr> <87y2ygw5ql.fsf@dell.be.48ers.dk> Message-ID: <87pnjr5ue3.fsf@geanix.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Peter Korsgaard writes: >>>>>> "Arnout" == Arnout Vandecappelle writes: > > Hi, > > > Does this also work if the tarball is cross-compiled for a different > > architecture? Probably it does, and it just SIGILLs when you try to run the > > container... > > Yes. Even easier is just > > docker import output/images/rootfs.tar > > > Yeah, except unfortunately docker security sucks, so on most distros you need > > sudo to run any docker command, even 'docker build'. > > > So, it would be nice if we could generate the OCI image without docker. > > I believe you can do similar with E.G. buildah: > > https://github.com/containers/buildah > > But you anyway need buildah/docker/.. to then finally do something with > the docker image afterwards, so perhaps just documenting the 'docker > import' oneliner is enough and not try to do it Buildroot. Sorry for the duplicate comment about buildah. To do something with an OCI image build with buildah, you should consider using podman (https://github.com/containers/libpod), as it also can be used without root priveleges, so should be feasible on shared servers. /Esben