linux:lxc:lxc-download

差分

このページの2つのバージョン間の差分を表示します。

この比較画面へのリンク

両方とも前のリビジョン 前のリビジョン
次のリビジョン
前のリビジョン
linux:lxc:lxc-download [2014/01/11 14:41] tenforwardlinux:lxc:lxc-download [2014/01/14 11:19] (現在) tenforward
行 1: 行 1:
 +(更新: 2014-01-14)
 +
 +メタデータのうち,
 +  * fstab は必須でなくなった (あれば上書き)
 +  * expiry も必須でなくなった (なければ expire しない)
 +
 +----
 +
 +(このページはメモです.そのうち消えるかも?)
 +
 これを読んだそのまま これを読んだそのまま
   * http://lists.linuxcontainers.org/pipermail/lxc-devel/2014-January/006992.html   * http://lists.linuxcontainers.org/pipermail/lxc-devel/2014-January/006992.html
行 192: 行 202:
  
   * (参考) http://lists.linuxcontainers.org/pipermail/lxc-devel/2014-January/007007.html   * (参考) http://lists.linuxcontainers.org/pipermail/lxc-devel/2014-January/007007.html
 +
 +----
 +Just a quick note for the new template you'd create to unpack this, to
 +hopefully save you a bit of frustration: as with the ubuntu-cloud
 +template, you have to do
 +
 +tar --anchored --exclude="dev/*" --numeric-owner -xpzf "$cache/$filename"
 +
 +and then create bind mount fstab entries for the crucial devices.
 +
 +----
 +pre-build にする理由
 +
 +<code>
 +> > Not an objection but a question to understand more. I'm assuming the
 +> > problem is the tools that used for bootstrapping (like
 +> > debootstrap/febootstrap etc.) requiring some privileges. If that's the
 +> > case, can't we write something (like setting suid bit or giving
 +> > required capabilities via libcap) to make unprivileged user to create
 +> > the container using regular templates?
 +
 +> The main problem we have at the moment is anything attempting to mknod.
 +> Then we have some templates like fedora which use loop mounts and other
 +> similar restricted kernel features.
 +
 +And to be clear, adding suid bits won't help as the templates run in a
 +user namespace.  Mounting block filesystems and creating devices are not
 +allowed there for now, period.
 +</code>
 +
  
  • linux/lxc/lxc-download.1389451281.txt.gz
  • 最終更新: 2014/01/11 14:41
  • by tenforward