All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Laniel <flaniel@linux.microsoft.com>
To: buildroot@buildroot.org, Arnout Vandecappelle <arnout@mind.be>
Cc: Gerome Burlats <gerome.burlats@smile.fr>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [RFC PATCH v1 0/1] New "docker" ready qemu config
Date: Thu, 21 Apr 2022 17:30:06 +0100	[thread overview]
Message-ID: <2626500.mvXUDI8C0e@pwmachine> (raw)
In-Reply-To: <6813316c-23f9-3521-1eca-df43f9205d34@mind.be>

Hi.

Le mardi 19 avril 2022, 22:16:43 BST Arnout Vandecappelle a écrit :
> On 14/04/2022 19:28, Francis Laniel wrote:
> > Hi.
> > 
> > 
> > First, I hope you are fine and the same for your relatives.
> > 
> > In this contribution, I added a new qemu config for x86_64.
> > This configuration is mainly based on qemu_x86_64_defconfig but it adds
> > kernel CONFIG_ to be able to use docker.
> > It also adds package related to docker like DOCKER_CLI and CONTAINERD.
> 
>   We don't like adding "demo" defconfigs that are basically another
> defconfig with some packages enabled. It's true that there is some value to
> knowing which combination of packages can provide a certain super-feature,
> but the problem is that the basic config (in this case, qemu_x86_64) is not
> going to be useful for most people.
> 
>   In this particular case, there isn't even that much "combination". Just
> docker-engine and docker-cli.
> 
>   The kernel config options do have value, but these should instead be set
> by containerd (or docker-engine, or docker-proxy, as appropriate), using
> CONTAINERD_LINUX_CONFIG_FIXUPS.

Sorry, I did not check docker-engine.mk before writing this contribution.
I was not aware of PACKAGE_NAME_LINUX_CONFIG_FIXUPS and will rework my sysdig 
0.29.1 contribution to make use ot it!

> 
>   Regards,
>   Arnout
> 
> > The CONFIG_ options added were checked with moby check-config script [1].
> > 
> > I was able to build and execute the image with start-qemu.sh:
> > Welcome to Buildroot
> > buildroot login: root
> > # docker run --rm hello-world
> > Unable to find image 'hello-world:latest' locally
> > latest: Pulling from library/hello-world
> > 2db29710123e: Pull complete
> > Digest:
> > sha256:10d7d58d5ebd2a652f4d93fdd86da8f265f5318c6a73cc5b6a9798ff6d2b2e67
> > Status: Downloaded newer image for hello-world:latest
> > 
> > Hello from Docker!
> > This message shows that your installation appears to be working correctly.
> > 
> > Sadly, the image has to a bit big (more than 300M) but I think it is fine
> > since this image will only be used for virtualization.
> > 
> > If you say any way to improve this contribution, feel free to share it!
> > 
> > Francis Laniel (1):
> >    qemu_x86_64_docker: add new qemu defconfig
> >   
> >   DEVELOPERS                             |   2 +
> >   board/qemu/x86_64_docker/linux.config  | 112 +++++++++++++++++++++++++
> >   board/qemu/x86_64_docker/post-build.sh |  11 +++
> >   board/qemu/x86_64_docker/readme.txt    |   7 ++
> >   configs/qemu_x86_64_docker_defconfig   |  49 +++++++++++
> >   5 files changed, 181 insertions(+)
> >   create mode 100644 board/qemu/x86_64_docker/linux.config
> >   create mode 100755 board/qemu/x86_64_docker/post-build.sh
> >   create mode 100644 board/qemu/x86_64_docker/readme.txt
> >   create mode 100644 configs/qemu_x86_64_docker_defconfig
> > 
> > Best regards and thank you in advance.
> > ---
> > [1] https://github.com/moby/moby/blob/master/contrib/check-config.sh

Best regards.


_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-04-21 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 17:28 [Buildroot] [RFC PATCH v1 0/1] New "docker" ready qemu config Francis Laniel
2022-04-14 17:28 ` [Buildroot] [RFC PATCH v1 1/1] qemu_x86_64_docker: add new qemu defconfig Francis Laniel
2022-04-19 21:16 ` [Buildroot] [RFC PATCH v1 0/1] New "docker" ready qemu config Arnout Vandecappelle
2022-04-21 16:30   ` Francis Laniel [this message]

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=2626500.mvXUDI8C0e@pwmachine \
    --to=flaniel@linux.microsoft.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=gerome.burlats@smile.fr \
    --cc=romain.naour@gmail.com \
    /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.