From: Danny Milosavljevic <dannym@scratchpost.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Release: Docker Image? DockerHub? skopeo?
Date: Tue, 17 Nov 2020 17:31:03 +0100 [thread overview]
Message-ID: <20201117173103.31703c84@scratchpost.org> (raw)
In-Reply-To: <86k0ums3xw.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Hi,
On Sun, 15 Nov 2020 22:30:51 +0100
zimoun <zimon.toutoune@gmail.com> wrote:
> Wow! The image is huge:
>
> 5.23GB registry.gitlab.com/daym/guix-on-docker latest 884b4a4ddf61
>
> Is it expected?
Yes, because Docker is silly. It will continue to grow.
It should be better when you use an external volume as /gnu/store and /var/guix.
> <https://yhetil.org/guix-user/CAKjnHz1X26QhPEWZfOmAbEmZHQA1qdU_Dq7U6kVXUqG7vCvuhw@mail.gmail.com>
> Then, the ’docker exec’ downloads \o/ and then fails with:
> guix pack: error: getting status of `/tmp': No such file or directory
>
> Hum, as in the other message, I am sure I am missing the obvious with
> Docker options.
Yeah, someone needs to create /tmp. That someone is not Guix (it would be weird).
/tmp is a common directory, so it does not belong to any of the parts that
have been composed, or maybe there should be a standard "/tmp" part?
Is there such a standard "/tmp" part in Docker-land?
Similarly, but worse, with /etc/passwd, /etc/group, /etc/services and so on.
> Currently, it builds master, right? I have not looked but do you think
> it could possible to track the both branches master and version-1.x.y?
Yes, right now it builds current master.
Sure, could easily make it do both.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-17 16:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 9:51 Releasing guix binary in Docker format too? Danny Milosavljevic
2020-09-23 11:07 ` 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 [this message]
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=20201117173103.31703c84@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).