From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id SQAGLkAntV8tBAAA0tVLHw (envelope-from ) for ; Wed, 18 Nov 2020 13:53:04 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id QOieKUAntV94BQAAB5/wlQ (envelope-from ) for ; Wed, 18 Nov 2020 13:53:04 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 6F970940105 for ; Wed, 18 Nov 2020 13:53:04 +0000 (UTC) Received: from localhost ([::1]:56312 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfNtP-000843-82 for larch@yhetil.org; Wed, 18 Nov 2020 08:53:03 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:41010) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfNtG-00082f-3O for guix-devel@gnu.org; Wed, 18 Nov 2020 08:52:54 -0500 Received: from 02c.relay.hey.com ([204.62.114.230]:13727) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfNtE-0005or-07 for guix-devel@gnu.org; Wed, 18 Nov 2020 08:52:53 -0500 Received: from hey.com (bigip-vip-new.rw-ash-int.37signals.com [10.20.0.24]) by 02.relay.hey.com (Postfix) with ESMTP id 97226160D28; Wed, 18 Nov 2020 13:52:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hey.com; s=heymail; t=1605707571; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=lIPG0m2D8F9gkLO7D7c/RRdBh03aVZlHLf1STaQaygg=; b=a9XNux48KbObsqv+2/MfMRiaBydvabp27aaVB36EtQJefN+haEa1TE/NTE4IxhS8eC/uvt zBTaeXwkkjNVRJ3nRqClwUDoqiktDLCh3HIwHEPbACj8YUvl9eijdp9fDwBdYLJMBFRou0 dScS+P5HB8sKJ21hMfzrDJgpvpnpg3DDV2A7Iw0HUzIbUBrm9O7GErWgh6qhRKvO9mf1kX vU03r2wH0Ji14I1eeauo7upgkk+X0OaGa6I+jDqOjO/ct08pIfKwuJC/AmUAkIZHarKYrr uf9zYAin9865fYEvoDZnI0B7ZkmUXuQvB3Qq/rlz+bjsQmU8u5sWnHJBRrj/Bw== Date: Wed, 18 Nov 2020 13:52:49 +0000 From: Ryan Prior To: Danny Milosavljevic , Bengt Richter Cc: Development of GNU Guix and the GNU System distribution Message-ID: In-Reply-To: <20201118125636.GA3085@LionPure> Subject: Re: Releasing guix binary in Docker format too? Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5fb5273233fa0_7af62dc854780"; charset=UTF-8 Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=204.62.114.230; envelope-from=ryanprior@hey.com; helo=02c.relay.hey.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/18 08:52:51 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=hey.com header.s=heymail header.b=a9XNux48; dmarc=pass (policy=quarantine) header.from=hey.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -0.21 X-TUID: KkocF00uP0zF ----==_mimepart_5fb5273233fa0_7af62dc854780 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On November 18, 2020, Bengt Richter wrote:=0D > E.g., (quoted from [1]), does the following mean that the guix daemon=0D= > potentially could run "projects"=0D > instead of guixbuilder* to create "Multiple isolated environments on a=0D= > single host" ?=0D > The features of Compose that make it effective are:=0D >=0D > =C2=A0Multiple isolated environments on a single host=0D > =C2=A0Preserve volume data when containers are created=0D > =C2=A0Only recreate containers that have changed=0D > =C2=A0Variables and moving a composition between environments=0D =0D I love docker-compose and have used it every day. There are a bunch of=0D= workflows I use compose for that I haven't figured out how to replace=0D with Guix yet, and I'm not in a huge hurry, but it would be great to see=0D= features that are designed to appeal to Compose users.=0D =0D For example, a common thing I do with docker-compose is to provide a=0D compose file with a service I'm working on that brings up the service=0D with all its dependencies (eg databases,=C2=A0 proxies, etc.) in a dev=0D= configuration, with the source code from the repository mapped into the=0D= container and live-reload enabled. That creates a "two-step" dev=0D environment for the service: you clone the repo then run "docker-compose=0D= up."=0D =0D Hashicorp has been working on Waypoint[1], a free software tool to=0D extend that concept even further by adding deployment and release=0D capabilities. Now you clone a repo and you have one tool to build,=0D deploy and release the software contained therein.=0D =0D I'm interested to use Guix for similar purposes, but there are a few=0D primary obstacles in the way:=0D 1) I don't have enough experience yet defining systems using Guix=0D similar to what I'd define using docker-compose, and I haven't found=0D documentation or examples yet that makes it seem within reach=0D 2) The machines I'm deploying to run Kubernetes, not Guix System, so if=0D= I do use Guix to build a bundle for deployment its utility ends when I=0D= export to a Docker container image.=0D 3) I collaborate with developers who use macOS and Windows and so can't=0D= easily install and use Guix.=0D =0D [1] https://www.waypointproject.io/=0D ----==_mimepart_5fb5273233fa0_7af62dc854780 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D
=0D
=0D
On November 18, 2020, Bengt Richter <bokr@bokr.com> wrote:
E.g., (quoted from [1]), does the following mean that the= guix daemon potentially could run "projects"
instead of gui= xbuilder* to create "Multiple isolated environments on a single host= " ?
The features of Compose that make it effective are:

=C2= =A0Multiple isolated environments on a single host
=C2=A0Preserve volu= me data when containers are created
=C2=A0Only recreate containers tha= t have changed
=C2=A0Variables and moving a composition between enviro= nments

I love docker-compose and have used it every = day. There are a bunch of workflows I use compose for that I haven't figu= red out how to replace with Guix yet, and I'm not in a huge hurry, but it= would be great to see features that are designed to appeal to Compose us= ers.

For example, a common thing I do with docker-compose is to pr= ovide a compose file with a service I'm working on that brings up the ser= vice with all its dependencies (eg databases,=C2=A0 proxies, etc.) in a d= ev configuration, with the source code from the repository mapped into th= e container and live-reload enabled. That creates a "two-step" = dev environment for the service: you clone the repo then run "docker= -compose up."

Hashicorp has been working on Waypoint[1], a fr= ee software tool to extend that concept even further by adding deployment= and release capabilities. Now you clone a repo and you have one tool to = build, deploy and release the software contained therein.

I'm inte= rested to use Guix for similar purposes, but there are a few primary obst= acles in the way:
1) I don't have enough experience yet defining syste= ms using Guix similar to what I'd define using docker-compose, and I have= n't found documentation or examples yet that makes it seem within reach2) The machines I'm deploying to run Kubernetes, not Guix System, so if= I do use Guix to build a bundle for deployment its utility ends when I e= xport to a Docker container image.
3) I collaborate with developers wh= o use macOS and Windows and so can't easily install and use Guix.

= [1] https://www.waypointproject.io/
=0D
=0D =0D =0D
=0D =0D =0D ----==_mimepart_5fb5273233fa0_7af62dc854780--