From: "Todor Kondić" <tk.code@protonmail.com>
To: Edouard Klein <edou@rdklein.fr>
Cc: help-guix@gnu.org
Subject: Re: guix pack and exposing ports
Date: Thu, 19 Aug 2021 09:54:28 +0000 [thread overview]
Message-ID: <kdbNIA_qLNR5Yua_9qmO7yUkUtohomTU-XtAcqyySDnOL6-3Td-Y4vjA7g4SnP1fj2lcpSo48UfnGeAzrhWMVZkOGbYFhqiZOouO7MnAvsc=@protonmail.com> (raw)
In-Reply-To: <87tujlixhh.fsf@rdklein.fr>
Thanks Edouard!
So far I'm trying to follow the route where additional things are built on top of the existing image. Also managed to trim the image to a very bearable ~150Mb once I trimmed the manifest to bare necessities.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, August 19th, 2021 at 11:40 AM, Edouard Klein <edou@rdklein.fr> wrote:
> Hi !
>
> From what I know, with guix pack you can only have the dependencies in
>
> the docker image, but you won't have anything to start or manage your
>
> software automatically. You need to invoke the correct command (with
>
> docker run, I believe).
>
> What you can do is create an operating-system declaration and use the
>
> guix system docker-image subcommand. Note that this is way more
>
> involved, as you need to create a shepherd service for your software.
>
> I quickly ran into docker limitations following this route, but
>
> depending on what you want to do this may be the way to go.
>
> The alternative is to use the guix pack image as the base image in a
>
> standard dockerfile.
>
> As for the size of the image, see this thread
>
> https://lists.gnu.org/archive/html/help-guix/2021-07/msg00064.html
>
> Good luck
>
> Todor Kondić writes:
>
> > Hello,
> >
> > Please bear with me since I am not that very docker savvy. As far as I understand, normally, one can expose certain ports in a docker description file. But, how to do that when using `guix pack -f docker` command where the docker recipe is hidden from the user?
> >
> > Also, I note I'm getting ~10 GiG image for a flimsy program depending on R and shiny. Somehow that doesn't feel right. :)
next prev parent reply other threads:[~2021-08-19 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 21:00 guix pack and exposing ports Todor Kondić
2021-08-19 9:40 ` Edouard Klein
2021-08-19 9:54 ` Todor Kondić [this message]
2021-08-20 8:20 ` zimoun
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='kdbNIA_qLNR5Yua_9qmO7yUkUtohomTU-XtAcqyySDnOL6-3Td-Y4vjA7g4SnP1fj2lcpSo48UfnGeAzrhWMVZkOGbYFhqiZOouO7MnAvsc=@protonmail.com' \
--to=tk.code@protonmail.com \
--cc=edou@rdklein.fr \
--cc=help-guix@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.
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).