unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: <guix-devel@gnu.org>
Subject: Releasing guix binary in Docker format too?
Date: Tue, 22 Sep 2020 11:51:05 +0200	[thread overview]
Message-ID: <20200922115019.08d40bec@scratchpost.org> (raw)

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

Hello,

I'm working with Heads on using Guix to build Heads' source code reproducibly.

Now, Heads has most of its stuff on CI servers that use Docker for a lot of
things.

Therefore, I used Guix pack in the usual way to create a recent Guix
binary release and then just loaded that into a docker container, using that to
run "guix build".

That got me thinking--this situation is pretty common.  Do you think it would
make sense to actually build and release a Docker container for Guix (not
guix system; just guix-the-package-manager)?

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?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-09-22  9:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  9:51 Danny Milosavljevic [this message]
2020-09-23 11:07 ` Releasing guix binary in Docker format too? Pjotr Prins
2020-09-23 12:53   ` zimoun
2020-09-24  7:59 ` Danny Milosavljevic
2020-10-20 10:29   ` zimoun
2020-10-21  9:12     ` Ludovic Courtès
2020-10-21 10:57       ` zimoun
2020-10-21 15:42         ` Ludovic Courtès
2020-11-04 14:43           ` Danny Milosavljevic
2020-11-06  9:59             ` Ludovic Courtès
2020-11-06 12:47               ` zimoun
2020-11-06 13:28                 ` Danny Milosavljevic
2020-11-08 17:33                   ` Ludovic Courtès
2020-11-15 18:30                   ` zimoun
2020-11-17 16:38                     ` Danny Milosavljevic
2020-11-18 12:56                       ` Bengt Richter
2020-11-18 13:52                         ` Ryan Prior
2020-11-18 14:25                           ` zimoun
2020-10-21 11:04       ` Size of package 'guix' zimoun
2020-10-21 15:44         ` Ludovic Courtès
2020-10-21 16:04           ` zimoun
2020-11-04 11:05 ` Release: Docker Image? DockerHub? skopeo? zimoun
2020-11-04 13:44   ` Jelle Licht
2020-11-04 14:50   ` Danny Milosavljevic
2020-11-15 21:30     ` zimoun
2020-11-17 16:31       ` Danny Milosavljevic
2020-11-17 16:50         ` Danny Milosavljevic
2020-11-17 17:30         ` zimoun
2020-11-17 19:23           ` Danny Milosavljevic
2020-11-17 19:28             ` Danny Milosavljevic
2020-11-17 21:44               ` Ryan Prior
2020-11-17 22:05               ` Carlo Zancanaro
2020-11-19  9:21             ` zimoun
2020-11-19 10:49               ` Danny Milosavljevic
2020-11-20 11:34                 ` /etc/passwd & co. in Docker images Ludovic Courtès
2020-11-20 18:53                   ` Ryan Prior
2020-11-22 16:00                   ` Danny Milosavljevic
2020-11-22 16:49                     ` Ryan Prior
2020-11-29 12:51                     ` Danny Milosavljevic
2020-12-05 15:08                       ` Ludovic Courtès

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=20200922115019.08d40bec@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).