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 mDcVB6Qsa1+OJgAA0tVLHw (envelope-from ) for ; Wed, 23 Sep 2020 11:08:20 +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 gPD6AqQsa1/LdAAAB5/wlQ (envelope-from ) for ; Wed, 23 Sep 2020 11:08:20 +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 A49F194053E for ; Wed, 23 Sep 2020 11:08:19 +0000 (UTC) Received: from localhost ([::1]:34752 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kL2dG-0001Mu-Ay for larch@yhetil.org; Wed, 23 Sep 2020 07:08:18 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:56526) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kL2cX-0001Ml-A7 for guix-devel@gnu.org; Wed, 23 Sep 2020 07:07:33 -0400 Received: from mail.thebird.nl ([94.142.245.5]:58420) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kL2cT-0002Jo-J8 for guix-devel@gnu.org; Wed, 23 Sep 2020 07:07:32 -0400 Received: by mail.thebird.nl (Postfix, from userid 1000) id 8B29B71BE; Wed, 23 Sep 2020 13:07:24 +0200 (CEST) Date: Wed, 23 Sep 2020 13:07:24 +0200 From: Pjotr Prins To: Danny Milosavljevic Subject: Re: Releasing guix binary in Docker format too? Message-ID: <20200923110724.ya72yatw7dsqqjfm@thebird.nl> References: <20200922115019.08d40bec@scratchpost.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200922115019.08d40bec@scratchpost.org> User-Agent: NeoMutt/20170113 (1.7.2) Received-SPF: pass client-ip=94.142.245.5; envelope-from=pjotr2020@thebird.nl; helo=mail.thebird.nl X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/23 07:07:25 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, 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: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; 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.01 X-TUID: 8zaWIRTS7gmf Hi Danny! On Tue, Sep 22, 2020 at 11:51:05AM +0200, Danny Milosavljevic wrote: > Now, Heads has most of its stuff on CI servers that use Docker for a lot of > things. It would be very interesting to have a Docker registry for a number of (complicated) Guix packages. We have bioinformatics packages living in channels such as http://git.genenetwork.org/guix-bioinformatics/guix-bioinformatics. Bonface built a GeneNetwork Docker image for CI. I would like to see Docker images for vgtools, gemma, sambamba and other products we are (co)developing. A Guix Docker container could be the starting point for live installs on highly divergent systems (including an HPC cluster we are building). > While I was researching gitlab, I came across a feature where they have their > own Docker container registry on there. Apparently, the Docker CLI can fetch > from whatever server the user wants! > > $ docker run [options] registry.gitlab.com/group/project/image [arguments] > > That got me thinking, we could easily also release Guix on something like > that. Is our HTTP webserver enough to have a Docker registry, without > installing extra stuff? > > $ docker run localhost/foo > Unable to find image 'localhost/foo:latest' locally > docker: Error response from daemon: Get "http://localhost/v2/": dial tcp 127.0.0.1:80: connect: connection refused. > > Aha! > > Do we want to do it? I say YES :). If we have a way to create these containers we can distribute them through http IPFS. We'll help write a nice discovery web interface which initially can be a simple web page. I don't think we need Docker containers for every package. But if there is a demand for a specific tool it can be very helpful to distribute software that way. In fact, one software I am writing depends on a host of programming languages including Python, Racket and Rust. A Guix Docker container is by far the simplest solution to distribute the software. And Guix containers are tiny - which is really nice. Pj.