From: "Ludovic Courtès" <ludo@gnu.org>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: 37083@debbugs.gnu.org
Subject: [bug#37083] [PATCH 0/1] (Help needed!) machine: Implement 'digital-ocean-environment-type'.
Date: Wed, 04 Sep 2019 14:08:10 +0200 [thread overview]
Message-ID: <87y2z45knp.fsf@gnu.org> (raw)
In-Reply-To: <875zmirizk.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 27 Aug 2019 12:38:23 +0200")
Hi Jakob,
Did you have a chance to try this out?
Thanks,
Ludo’.
Ludovic Courtès <ludo@gnu.org> skribis:
> Hi Jakob,
>
> Nice that you’re working on Digital Ocean support!
>
> zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) skribis:
>
>> 'deploy-digital-ocean' gets to a point where there's a droplet running a
>> "bootstrap" configuration of the Guix System, but I can't keep an open
>> SSH channel for sending over the operating-system configuration
>> specified for the deployment.
>
> [...]
>
>> (services
>> (append (list (static-networking-service "eth0" "~a"
>> #:netmask "~a"
>> #:gateway "~a"
>> #:name-servers '("84.200.69.80" "84.200.70.40"))
>> (service openssh-service-type
>> (openssh-configuration
>> (permit-root-login 'without-password))))
>> %base-services)))
>
> Could you add (log-level 'debug) to ‘openssh-configuration’, then try
> again ‘guix deploy’, and finally grab the OpenSSH log from that machine?
> That would allow us to see if there’s something wrong with SSH.
>
> Hmm now that I think about it, ‘send-files’ may be failing because the
> (guix …) modules aren’t in GUILE_LOAD_PATH on the remote side. On the
> berlin build machines, we have this:
>
> (simple-service 'guile-load-path-in-global-env
> session-environment-service-type
> `(("GUILE_LOAD_PATH"
> . "/run/current-system/profile/share/guile/site/2.2")
> ("GUILE_LOAD_COMPILED_PATH"
> . ,(string-append "/run/current-system/profile/lib/guile/2.2/site-ccache:"
> "/run/current-system/profile/share/guile/site/2.2"))))
>
> It’s ridiculous that we have to do this, but that’s how it is.
>
> Can you try that?
>
> HTH,
> Ludo’.
next prev parent reply other threads:[~2019-09-04 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 16:41 [bug#37083] [PATCH 0/1] (Help needed!) machine: Implement 'digital-ocean-environment-type' Jakob L. Kreuze
2019-08-19 16:43 ` [bug#37083] [PATCH 1/1] " Jakob L. Kreuze
2019-08-27 10:38 ` [bug#37083] [PATCH 0/1] (Help needed!) " Ludovic Courtès
2019-09-04 12:08 ` Ludovic Courtès [this message]
2019-09-05 14:15 ` Jakob L. Kreuze
2019-09-07 20:10 ` Jakob L. Kreuze
2019-09-08 19:37 ` Ludovic Courtès
2019-09-21 20:56 ` Jakob L. Kreuze
2019-09-23 8:24 ` Ludovic Courtès
2019-09-28 20:46 ` Jakob L. Kreuze
2019-09-28 20:47 ` [bug#37083] [PATCH] " Jakob L. Kreuze
2019-09-28 22:36 ` Ludovic Courtès
2019-10-13 10:56 ` Ludovic Courtès
2019-10-22 16:34 ` Ludovic Courtès
2019-10-22 20:56 ` Jakob L. Kreuze
2019-10-23 9:42 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2z45knp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37083@debbugs.gnu.org \
--cc=zerodaysfordays@sdf.lonestar.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.