From: Florian Hoertlehner <hoertlehner@gmail.com>
To: 50977@debbugs.gnu.org
Subject: bug#50977: digital-ocean-environment-type fails
Date: Sat, 2 Oct 2021 21:49:49 +0200 [thread overview]
Message-ID: <CADXXfWk7DFjDNcxZ6f4Qsk3HiFpNz6m-0fm4pwYsjo58Kn6z1A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2817 bytes --]
guix deploy leads to the following error:
https://api.digitalocean.com/v2/droplets: HTTP post failed: 422
("Unprocessable Entity")
The token that I use seems to be correct (there comes a different error
message when I define an invalid token).
This is the config file:
(use-modules
(gnu services admin))
(use-service-modules networking ssh web)
(use-package-modules bootloaders ssh)
(define %system
(operating-system
(host-name "atlanticocean")
(timezone "Etc/UTC")
(bootloader (bootloader-configuration
(bootloader grub-bootloader)
(target "/dev/vda")
(terminal-outputs '(console))))
(file-systems (cons (file-system
(mount-point "/")
;; Must be vda2 or you won't be able to reboot
after `guix deploy`.
;; This is because our base image makes an EFI
partition at vda1.
(device "/dev/vda2")
(type "ext4"))
%base-file-systems))
(services
(append (list (service dhcp-client-service-type)
(service openssh-service-type
(openssh-configuration
(openssh openssh-sans-x)
(password-authentication? #false)
(permit-root-login #t)
(authorized-keys
;; Authorise our SSH key.
`(("root" ,(local-file "id_rsa.pub"))))))
;; Security updates, yes please!
(service unattended-upgrade-service-type)
;; Note that Nginx isn't automatically restarted during
;; `guix deploy`, so run `herd restart nginx`.
)
(modify-services %base-services
;; The server must trust the Guix packages you build. If you
add the signing-key
;; manually it will be overridden on next `guix deploy` giving
;; "error: unauthorized public key". This automatically adds
the signing-key.
(guix-service-type config =>
(guix-configuration
(inherit config)
(authorized-keys
(append (list (local-file
"/etc/guix/signing-key.pub"))
%default-authorized-guix-keys)))))))))
(define c-do
(digital-ocean-configuration
(region "nyc1")
(size "s-1vcpu-1gb")
(enable-ipv6? #f)
(ssh-key "/home/f/repo/myLinux/data/ssh/f")
(tags (list "ubuntu-s-1vcpu-1gb-nyc1-01"
))
))
(list (machine
(operating-system %system)
(environment digital-ocean-environment-type)
(configuration c-do)))
[-- Attachment #2: Type: text/html, Size: 4464 bytes --]
next reply other threads:[~2021-10-02 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 19:49 Florian Hoertlehner [this message]
2021-10-18 11:08 ` bug#50977: digital-ocean-environment-type fails Franz Geffke
2021-10-18 19:40 ` Franz Geffke
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=CADXXfWk7DFjDNcxZ6f4Qsk3HiFpNz6m-0fm4pwYsjo58Kn6z1A@mail.gmail.com \
--to=hoertlehner@gmail.com \
--cc=50977@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).