From: David Dashyan <mail@davie.li>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Build docker image
Date: Tue, 27 Apr 2021 20:11:51 +0300 [thread overview]
Message-ID: <87h7jrodns.fsf@davie.li> (raw)
In-Reply-To: <87r1j7kl6r.fsf@disroot.org>
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
next prev parent reply other threads:[~2021-04-27 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 3:49 Build docker image Bone Baboon
2021-04-17 20:05 ` David Dashyan
2021-04-19 3:27 ` Bone Baboon
2021-04-27 17:11 ` David Dashyan [this message]
2021-04-27 17:16 ` David Dashyan
2021-04-19 3:48 ` Bone Baboon
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=87h7jrodns.fsf@davie.li \
--to=mail@davie.li \
--cc=bone.baboon@disroot.org \
--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).