Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com>
To: buildroot@busybox.net
Subject: [Buildroot] [All Systems Go!] Buildroot : Using embedded tools to build container images
Date: Mon, 23 Sep 2019 09:44:36 +0200	[thread overview]
Message-ID: <87pnjr5ue3.fsf@geanix.com> (raw)
In-Reply-To: <87y2ygw5ql.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Sun, 22 Sep 2019 20:22:42 +0200")

Peter Korsgaard <peter@korsgaard.com> writes:

>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> 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 <myproject:mytag>
>
>  >  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

  reply	other threads:[~2019-09-23  7:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21 19:53 [Buildroot] [All Systems Go!] Buildroot : Using embedded tools to build container images Romain Naour
2019-09-22 13:13 ` François Perrad
2019-09-22 14:58   ` Arnout Vandecappelle
2019-09-22 15:47     ` Jérémy ROSEN
2019-09-22 16:46       ` Arnout Vandecappelle
2019-09-22 21:48         ` Jérémy ROSEN
2019-09-22 18:07     ` François Perrad
2019-09-23  7:17       ` Arnout Vandecappelle
2019-09-22 18:22     ` Peter Korsgaard
2019-09-23  7:44       ` Esben Haabendal [this message]
2019-09-23  7:49         ` Arnout Vandecappelle
2019-09-23  8:10           ` Esben Haabendal
2019-09-23  7:40     ` Esben Haabendal

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=87pnjr5ue3.fsf@geanix.com \
    --to=esben@geanix.com \
    --cc=buildroot@busybox.net \
    /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