All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] add option to run docker with initramfs
Date: Wed, 12 Jun 2019 22:18:56 +0200	[thread overview]
Message-ID: <20190612201856.GH2647@scaer> (raw)
In-Reply-To: <CAL+Nh7PQaDFU_SrWoV_W7-H=s6Y4ALHeC3A_LUozY+SnyXo3Lw@mail.gmail.com>

Frank, All,

On 2019-06-12 19:18 +0300, Fragkiskos Sigalas spake thusly:
> By default docker uses pivot_root which is not available in initramfs.

pivot_root is provided by either util-linux or busybox; it has (AFAICT)
no relation to whether running from an initramfs or any other filesystem).

Our default configuration for busybox eeven enables pivot_root.

So, it looks like your could very well add pivot_root to your initramfs,
in fact.

Regards,
Yann E. MORIN.

> The way to override the default behaviour is to define an
> environment variable DOCKER_RAMDISK when starting the daemon (weirdly enough there appears to be no respective command line option).
> Would it make sense to add such an option in the docker package?



-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-06-12 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 16:18 [Buildroot] add option to run docker with initramfs Fragkiskos Sigalas
2019-06-12 20:18 ` Yann E. MORIN [this message]
2019-06-12 21:41   ` Christian Stewart
2019-06-12 21:53   ` Fragkiskos Sigalas

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=20190612201856.GH2647@scaer \
    --to=yann.morin.1998@free.fr \
    --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.