unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: wolf <wolf@wolfsden.cz>,
	Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
	help-guix <help-guix@gnu.org>
Subject: Re: VSCode DevContainer for Guix? (Yasuaki Kudo)
Date: Thu, 13 Jul 2023 08:50:56 +0900	[thread overview]
Message-ID: <166FB56B-E6C0-4B6E-9FE3-045B97444936@yasuaki.com> (raw)
In-Reply-To: <1YPgbJzod_8jQRMq7iKAFz4n-VXHvWaDz7aqRkyPg9VHHo8Pwogw5Gjlj3rPjoK3Me4DfjBBT2YlyZ0UKuAMynzkSaf3aBMV2pKbCwl--B0=@elenq.tech>

Thank you for this, yes, this is exactly the kind if idea I had in mind, although I was assuming that Guix docker would be super bare bones by almost default 😄

I think keeping the core of your software benefits the entire system, making it secure and keeping the cost down for storage, hosting and running.

So that's why I am interested 😄

-Yasu

> On Jul 12, 2023, at 20:27, Ekaitz Zarraga <ekaitz@elenq.tech> wrote:
> 
> 
>> Careful about this assumption, Guix-generated container images are pretty large
>> and include a lot of things you might not want in there (man, info pages, bash,
>> ...). I am not saying "do not use it", but if you try to convince people to use
>> Guix for container builds, size should not be your argument (especially since
>> Alpine exists as an alternative).
> 
> That is very true.
> This week in System Crafters they have been workin on trying to reduce this. But I didn't have the time to watch the results deeply.
> Be careful, youtube link:
> https://www.youtube.com/watch?v=ItGRcOLT-BM


  reply	other threads:[~2023-07-12 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.87.1689091255.20905.help-guix@gnu.org>
2023-07-11 19:23 ` VSCode DevContainer for Guix? (Yasuaki Kudo) Zelphir Kaltstahl
2023-07-12  1:22   ` Yasuaki Kudo
2023-07-12  8:27     ` wolf
2023-07-12 11:27       ` Ekaitz Zarraga
2023-07-12 23:50         ` Yasuaki Kudo [this message]
2023-08-23 15:12       ` Simon Tournier

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=166FB56B-E6C0-4B6E-9FE3-045B97444936@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=ekaitz@elenq.tech \
    --cc=help-guix@gnu.org \
    --cc=wolf@wolfsden.cz \
    --cc=zelphirkaltstahl@posteo.de \
    /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. 
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).