From: Efraim Flashner <efraim@flashner.co.il>
To: jimmy@thrasibule.mx
Cc: help-guix@gnu.org
Subject: Re: system docker-image needs file-system
Date: Thu, 16 Jan 2020 09:31:40 +0200 [thread overview]
Message-ID: <20200116073140.GN858@E5400> (raw)
In-Reply-To: <CAMqSRmBBUn77jqg_6PRYBBASD0uLTcX8ZSkFF5KP2X3LPzdACQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]
On Wed, Jan 15, 2020 at 11:43:25PM +0100, Jimmy Thrasibule wrote:
> I got it working by using
>
>
> (bootloader (bootloader-configuration
> (bootloader grub-efi-bootloader)
> (target "noop")))
>
> (file-systems (list (file-system
> (device "noop")
> (mount-point "/")
> (type "noop"))))
>
>
> Your suggestion seems to be working for (file-systems) but not (bootloader):
>
> Wrong type argument in position 1 (expecting struct): #f
Here's what I typically use for my guix system containers:
(bootloader (bootloader-configuration
(bootloader grub-bootloader)
(target "does-not-matter")))
(file-systems %base-file-systems)
;; No firmware for VMs.
(firmware '())
;; We don't need any packages inside the container.
(packages '())
Based on other discussions, it seems that (bootloader #f) may also work.
>
>
> Le mer. 15 janv. 2020 à 21:19, Julien Lepiller <julien@lepiller.eu> a
> écrit :
>
> > Le 15 janvier 2020 15:01:18 GMT-05:00, Josh Marshall <
> > joshua.r.marshall.1991@gmail.com> a écrit :
> > >I'll second this. It is one of my expected use cases.
> > >
> > >On Wed, Jan 15, 2020, 13:32 Jimmy Thrasibule
> > ><jimmy.thrasibule@gmail.com>
> > >wrote:
> > >
> > >> Hi,
> > >>
> > >> I'm trying to use Guix in order to create a Docker image. However,
> > >I'm
> > >> forced to set both ``bootloader`` and ``file-systems`` initializers:
> > >>
> > >> system.scm:29:0: error: missing field initializers (bootloader
> > >> file-systems)
> > >>
> > >> For a Docker image this is quite unexpected. I'm wondering whether
> > >there is
> > >> a way to bypass this limitation?
> > >>
> > >> Regards,
> > >> Jimmy
> > >>
> >
> > Not sure if that will work, but have you tried:
> >
> > (bootloader #f)
> > (file-systems '())
> >
> > ?
> >
> >
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-16 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 16:17 system docker-image needs file-system Jimmy Thrasibule
2020-01-15 20:01 ` Josh Marshall
2020-01-15 20:19 ` Julien Lepiller
2020-01-15 22:43 ` Jimmy Thrasibule
2020-01-16 7:31 ` Efraim Flashner [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200116073140.GN858@E5400 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=jimmy@thrasibule.mx \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).