From: Lennart Poettering <lennart@poettering.net>
To: arnaud gaboury <arnaud.gaboury@gmail.com>
Cc: systemd <systemd-devel@lists.freedesktop.org>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs
Date: Thu, 23 Apr 2015 13:50:56 +0200 [thread overview]
Message-ID: <20150423115056.GA28566@gardel-login> (raw)
In-Reply-To: <CAK1hC9ujeQs_pv6nD6C689hMFQNjMMQdUgt7RFOz0gHjdeSz_A@mail.gmail.com>
On Thu, 23.04.15 13:45, arnaud gaboury (arnaud.gaboury@gmail.com) wrote:
> Not sure what I did wrong, but I can't install/boot my nspawn container.
> Here is my setup:
>
> Archlinux box- updated
>
> 1- created 3 btrfs subvol on /dev/sdb1 (SSD). The goal is to manage
> snapshots easily.
> no nested subvol.
> ------------------------------------------
> # btrfs subvolume list .
> ID 266 gen 39 top level 5 path rootvol
> ID 268 gen 41 top level 5 path var
> ID 269 gen 42 top level 5 path etc
> # btrfs filesystem show
> Label: 'poppy-root' uuid: ef1b44cd-e7b0-4166-b933-e7d4d20a1171
> Total devices 1 FS bytes used 64.00KiB
> devid 1 size 80.00GiB used 12.00MiB path /dev/sdb1
> --------------------------------------------------
>
> 2 - mount btrfs subvol
> -------------------------------------------------------------------
> # mount -t btrfs -o subvol=rootvol /dev/sdb1 /var/lib/machines/enl
> # mkdir /var/lib/machines/enl/var
> # mkdir /var/lib/machines/enl/etc
> # mount -t btrfs -o subvol=etc /dev/sdb1 /var/lib/machines/enl/etc
> # mount -t btrfs -o subvol=var /dev/sdb1 /var/lib/machines/enl/var
> --------------------------------------------------------------------
THis isn't really how one would normally use subvolumes. No need to
mount each subvolume explicitly, they are just special directories...
>
> 3- install fedora minimal and boot it
> -------------------------------------------------
> # machinectl pull-raw --verify=no
> http://ftp.halifax.rwth-aachen.de/fedora/linux/releases/22/Cloud/Images/x86_64/Fedora-Cloud-Base-22_Beta-20150415-x86_64.raw.xz
> $ tar ....
> # systemd-nspawn -M Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw
> Spawning container Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw on
> /var/lib/machines/Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw.
> Press ^] three times within 1s to kill container.
> [root@Fedora-Cloud-Base-22_Beta-20150415 ~]#
> ------------------------------------------------------------
>
> 4- install Fedora on /var/lib/machines/enl
> --------------------------------------------------------------
> [root@Fedora-Cloud-Base-22_Beta-20150415 ~]# dnf -y --releasever=22
> --nogpg --installroot=/var/lib/machines/MyContainer --disablerepo='*'
> --enablerepo=fedora install systemd passwd dnf fedora-release-server
> vim-minimal
> ..........................
> INSTALL
> ...........................
> Complete!
> ----------------------------------------------------------
Hmm? With this command you installed another fedora inside the raw
fedora image you downloaded. You now have three linuxes, installed
within each other...
Pick one:
a) download the raw image and use that, but it will be a loopback file
with its own file system inside
or:
b) do the dnf/yum install root thing, and install it into a directory
tree.
Do either of those in the host, not in the container.
Lennart
--
Lennart Poettering, Red Hat
next prev parent reply other threads:[~2015-04-23 11:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 11:45 install Fedora systemd-nspawn container on btrfs arnaud gaboury
2015-04-23 11:50 ` Lennart Poettering [this message]
2015-04-23 11:57 ` [systemd-devel] " Andrei Borzenkov
2015-04-23 12:00 ` Lennart Poettering
2015-04-23 12:20 ` arnaud gaboury
2015-04-23 12:18 ` arnaud gaboury
2015-04-23 14:47 ` Lennart Poettering
2015-04-23 17:00 ` arnaud gaboury
2015-04-23 17:12 ` Lennart Poettering
2015-04-23 17:21 ` arnaud gaboury
2015-04-23 17:29 ` arnaud gaboury
2015-04-23 17:36 ` Lennart Poettering
2015-04-23 17:37 ` arnaud gaboury
2015-04-24 6:14 ` arnaud gaboury
2015-04-24 6:16 ` arnaud gaboury
2015-04-24 6:30 ` arnaud gaboury
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=20150423115056.GA28566@gardel-login \
--to=lennart@poettering.net \
--cc=arnaud.gaboury@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.org \
/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.