From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Running code from packs in containers
Date: Tue, 30 Jan 2018 18:21:34 +0100
Message-ID: <87d11rxnxd.fsf_-_@gnu.org>
References: <87vag2wopo.fsf@gnu.org> <877esh3gwd.fsf@gnu.org>
	<87tvvlrzlc.fsf@gnu.org> <87efmeuhvb.fsf@gnu.org>
	<87zi51r3cg.fsf@gnu.org> <87po5xgtue.fsf@gnu.org>
	<87lgggligx.fsf@gnu.org> <87k1w0rsud.fsf@elephly.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55792)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1egZbJ-0003cB-HP
	for help-guix@gnu.org; Tue, 30 Jan 2018 12:21:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1egZbG-0000Ek-AC
	for help-guix@gnu.org; Tue, 30 Jan 2018 12:21:41 -0500
In-Reply-To: <87k1w0rsud.fsf@elephly.net> (Ricardo Wurmus's message of "Tue,
	30 Jan 2018 03:19:38 +0100")
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-guix/>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Court=C3=A8s <ludo@gnu.org> writes:
>
>> Actually there are really two approaches we could use.  One is to create
>> wrappers like this one that do the right thing, independently of what
>> the user=E2=80=99s profile contains (=E2=80=98guix package=E2=80=99 coul=
d even generate wrappers
>> automatically in some cases.)
>>
>> The second approach is a =E2=80=98guix run/environment=E2=80=99 kind of =
command that
>> generates the environment at run time.
>>
>> There are pros and cons to both, I think.
>
> This is just a tangent:
>
> I=E2=80=99ve been thinking that =E2=80=9Cguix run=E2=80=9D (or an extensi=
on of =E2=80=9Cguix container=E2=80=9D)
> would be great not only for running applications in containers that are
> *already* in the store, but also to run applications from tarballs that
> were generated with "guix pack=E2=80=9C.
>
>     pack=3D$(guix pack $(readlink -f $HOME/.guix-profile) -S /bin=3Dbin)
>     guix run --image=3D${pack} /bin/icecat
>
> Look, we=E2=80=99ve got our own container image format! :) This seems to =
cover
> 85% of all uses of Docker/Singularity in the field of bioinformatics.

Indeed, very good point!

> The setup to create configuration files and set environment variables so
> that the target application feels at home in the container =E2=80=94 that=
 all
> looks an awful lot like profile hooks to me.  Maybe we can have a set of
> common hooks that we can automatically derive from package inputs?

Sounds like search paths no?  Or maybe a bit of both?

Anyway, it wouldn=E2=80=99t cost us much so to speak, so it=E2=80=99s worth=
 looking into
that.

Ludo=E2=80=99.