[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Build docker image
From: |
David Dashyan |
Subject: |
Re: Build docker image |
Date: |
Tue, 27 Apr 2021 20:11:51 +0300 |
User-agent: |
mu4e 1.4.15; emacs 27.2 |
Hello Bone Baboon!
Great to hear that you got it working!
Bone Baboon writes:
> David Dashyan writes:
>> It is not 100% clear from your message how do you want to build a docker
>> image. I'm assuming that you want to use standard docker tooling and
>> you want to have docker daemon on YOUR system. Correct me I'm wrong
>> here.
>
> Yes that is correct `docker build -t <tag> .` with a local docker
> daemon.
>
>> Dockder service is one of the services that extends
>> shepherd-root-service-type. They form dependency graph which is
>> different from extension graph you might have red in guix manual. Each
>> shepherd service has "provision" field that defines list of simbols that
>> it provides and "requirement" field (defaulting to '()) that defines
>> which services it requeres to run. Shepherd uses this information to
>> spawn services in right order. But in your case procedure
>> assert-valid-graph (found in guix) warned you that graph is invalid
>> instead of producing shepherd configuration that will fail when you will
>> boot.
>
> This is a nice feature.
>
>> So. You need a service that provisionts 'networking!
>
> It seems odd that a service does not take care of services it needs.
> It makes me think of a package that does not include the dependencies it
> needs to run.
I'm not sure why it is done this way. Perhaps because you could have
different service types providing same provision symbols? And you as a
user/admin chose which to chose. And also the dependency graph of guix
services enourmos as package dependency graph :)
--
David aka zzappie