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 10:10:52 +0200 [thread overview]
Message-ID: <87lfuf5t6b.fsf@geanix.com> (raw)
In-Reply-To: <b40aa877-9deb-7052-0e26-0970708f9fd9@mind.be> (Arnout Vandecappelle's message of "Mon, 23 Sep 2019 09:49:26 +0200")
Arnout Vandecappelle <arnout@mind.be> writes:
> On 23/09/2019 09:44, Esben Haabendal wrote:
>> 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.
>
> I may be wrong, but as I understand it, all these tools actually call docker
> under the hood.
You are wrong. Buildah and Podman does not call docker in any way.
> They can be used without root privileges because they are
> installed with all the necessary suid bits and caps and stuff.
No suid bit.
> However, AFAIU, you can't build and install them as non-root and then
> create an image with it.
System must be configured to allow normal users to run unprivileged
containers (sysctl kernel.unprivileged_userns_clone=1). Setting this
naturally requires privileges.
> umoci was the only tool I found that seemed to *really* not require
> root.
I suspect that there might some restrictions on what is possible when
using umoci as an unprivileged user (see
https://umo.ci/quick-start/rootless/).
/Esben
next prev parent reply other threads:[~2019-09-23 8:10 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
2019-09-23 7:49 ` Arnout Vandecappelle
2019-09-23 8:10 ` Esben Haabendal [this message]
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=87lfuf5t6b.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.