From: Eddy Pronk <epronk@muftor.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: guixsd in lxd container
Date: Sat, 10 Jun 2017 14:53:24 +1000 [thread overview]
Message-ID: <CAErGuQiMTPNu9uFVuruP-WRiHnx9sbL1FigAZF+Z=_t6Hcdf+w@mail.gmail.com> (raw)
In-Reply-To: <87h8zo3jzk.fsf@gnu.org>
On Sat, Jun 10, 2017 at 7:54 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>> When a container start it runs /sbin/init.
>
> You mean LXD expects to run /sbin/init, right?
Yes, and the LXD container can be configured to run any other program instead.
> The line that’s printed here comes from (gnu build activation):
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/activation.scm#n442
>
> As you can see, it takes the value of ‘system’ either from the kernel’s
> ‘--system’ command-line argument (/proc/cmdline), or from the
> ‘GUIX_NEW_SYSTEM’ environment variable.
>
> So you’d have to set ‘GUIX_NEW_SYSTEM’ in your case to fix this.
Added this to my start script:
export GUIX_NEW_SYSTEM=/gnu/store/kq71yhydfgc0nksvmmn66cbvbj5a3mvf-system
Great. That works. This got me 2 steps further.
I had to comment out some snippets from activation.scm:
;; activate-modprobe
;; activate-firmware
;; activate-ptrace-attach
(I actually edited the 1 line snippets that get generated somehow.)
Now the boot script starts shepherd.
>> Service file-system-/tmp has been started.
>> failed to start service 'file-systems' <<== first problem.
>> failed to start service 'file-system-/dev/pts'
>
> What ‘guix system container’ does to work around this is to try to mount
> only file systems that can really be mounted inside a container, with
> the right options:
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/system/linux-container.scm#n37
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/system/file-systems.scm#n325
I'd like to get some logging out of the "failed to start service
'file-systems'".
When /sbin/init starts the usb-install image is already mounted on '/'.
What I see as pstree is:
---shepherd-+-udevd
`-{shepherd}
failed to start service 'term-tty1' is the last thing I see.
Can someone post a full log of the shepherd startup?
> BTW, did you consider using ‘guix system container’ directly instead of
> LXC? It’s not perfect but probably worth a try:
I'll give that a try. Maybe just to learn how it does it.
For Ubuntu users (or others distros with LXD) it would be a nice
managed way of trying out GuixSD if I get this to work.
Cheers,
Eddy
next prev parent reply other threads:[~2017-06-10 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 13:08 guixsd in lxd container Eddy Pronk
2017-06-09 21:54 ` Ludovic Courtès
2017-06-10 4:53 ` Eddy Pronk [this message]
2017-06-10 5:30 ` Jan Nieuwenhuizen
2017-06-11 20:26 ` Ludovic Courtès
2017-06-16 12:21 ` Eddy Pronk
2017-06-19 11:41 ` Ludovic Courtès
2017-06-20 12:35 ` Eddy Pronk
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='CAErGuQiMTPNu9uFVuruP-WRiHnx9sbL1FigAZF+Z=_t6Hcdf+w@mail.gmail.com' \
--to=epronk@muftor.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.