Hi zimoun,
On Thu, 19 Nov 2020 10:21:16 +0100
zimoun wrote:
> Let’s postpone this Docker image work and start a new fresh thread once
> v1.2.0 is published and the goal to have something for v1.3.0, well
> that’s my point of view.
After Ryan Prior's E-Mail I'm pretty sure my workaround of creat
Hi Danny,
Thank you for the explanations. Make sense. :-)
On Tue, 17 Nov 2020 at 20:23, Danny Milosavljevic
wrote:
> No, I don't use docker that much--and when I do, it's to run simple images
> others have created. So I just really don't know how this is supposed to
> be set up. I mean ther
Hey Danny,
On Wed, Nov 18 2020, Danny Milosavljevic wrote:
Hmm, maybe I'm misunderstanding what Docker compose does
entirely.
Reading the docs it seems to just manage multiple isolated
Docker images and deploy new ones?
Yep, that's all it does. It lets you link together ports and
volumes,
On November 17, 2020, Danny Milosavljevic
wrote:
> Hmm, maybe I'm misunderstanding what Docker compose does entirely.
What docker-compose does is it creates a set of Docker containers for
you based on a configuration file. In that file you define services,
filesystem volumes and their mount point
Hmm, maybe I'm misunderstanding what Docker compose does entirely.
Reading the docs it seems to just manage multiple isolated Docker images and
deploy new ones?
What then is used to do the equivalent of a guix profile with multiple packages
in a Docker image?
pgpxTzXrSUfaY.pgp
Description: Open
Hi zimoun,
On Tue, 17 Nov 2020 18:30:57 +0100
zimoun wrote:
> > Yeah, someone needs to create /tmp. That someone is not Guix (it
> > would be weird).
>
> Created where?
Created when creating the docker image--presumably by Docker when evaluating
Composefile.
AFAIK Docker images are suppose
Hi Danny,
On Tue, 17 Nov 2020 at 17:31, Danny Milosavljevic
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.
Oh, bad news! 5.23GB is already too muc
Hi,
> Yeah, someone needs to create /tmp. That someone is not Guix (it would be
> weird).
There is a workaround in /with-guix-daemon.scm in that guix-on-docker container,
which is how I'm using it.
The entrypoint I'm using (with the unmodified guix-on-docker image) is
["guix", "repl", "--"
Hi,
On Sun, 15 Nov 2020 22:30:51 +0100
zimoun 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/stor
Hi Danny,
Sorry to be late.
On Wed, 04 Nov 2020 at 15:50, Danny Milosavljevic
wrote:
>> Some days ago, we discussed on #guix about releasing Docker images
>> ready-to-use. And you pointed your project:
>>
>> https://gitlab.com/daym/guix-on-docker/
[...]
> For the use case I'm using it fo
Hi zimoun,
On Wed, 04 Nov 2020 12:05:28 +0100
zimoun wrote:
> Some days ago, we discussed on #guix about releasing Docker images
> ready-to-use. And you pointed your project:
>
> https://gitlab.com/daym/guix-on-docker/
>
> First question for Danny: is it ready to include it to the release?
Hello,
zimoun writes:
> Some days ago, we discussed on #guix about releasing Docker images
> ready-to-use. And you pointed your project:
>
> https://gitlab.com/daym/guix-on-docker/
[snip]
> Fourth question for Jelle: do you have time to add examples to the
> Cookbook using the package ’skop
Hi,
Some days ago, we discussed on #guix about releasing Docker images
ready-to-use. And you pointed your project:
https://gitlab.com/daym/guix-on-docker/
First question for Danny: is it ready to include it to the release?
Include meaning communicate about it – with the status experimental.
13 matches
Mail list logo
