all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Devan <mail@dvn.me>
Cc: guix-devel@gnu.org
Subject: Re: Orchestration working group (before: Guix orchestration notes)
Date: Sun, 04 Mar 2018 21:42:29 +0100	[thread overview]
Message-ID: <874llvh8sq.fsf@gmail.com> (raw)
In-Reply-To: <20180304021839.j7ittjuexbzdjtuj@kowloon> (Devan's message of "Sun, 4 Mar 2018 03:18:39 +0100")

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

Devan <mail@dvn.me> writes:

> Hi all,
>
> Pjotr Prins transcribed 0.6K bytes:
>> Hi Chris,
>> 
>> That was a lengthy writeup, thanks :). I think the first step is to
>> think in terms of (container/VM) provisioning. Then build that up towards
>> orchestration and workflows.
>
> I agree. I think a good start would be figuring out ways to
> essentially replace what you can do with Dockerfiles. Which to me 
> mainly means having the ability to arbitrarily copy files into, and 
> further manipulate the tarballs made from using `guix pack`.

With "guix pack", you can already create a Docker image that contains
arbitrary files.  Just define whatever packages you need in order to
install the things you want, and "guix pack --format=docker" will create
a Docker image of exactly what you declare, without building upon any
existing Docker image.  Is this different from what you had in mind?

Once "guix system docker-image" gets added, you will be able to do the
same thing for an entire GuixSD system:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30572

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-03-04 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18  4:37 Guix orchestration notes Chris Marusich
2018-03-01 16:18 ` Orchestration working group (before: Guix orchestration notes) Pjotr Prins
2018-03-04  2:18   ` Devan
2018-03-04 20:42     ` Chris Marusich [this message]
2018-03-27 18:27 ` Guix orchestration notes Thompson, David

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=874llvh8sq.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@dvn.me \
    /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.