unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Samuel Willey <samuelwilley@hotmail.com>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: oci-container-service-type: Wrong type argument in position 1 (expecting struct)
Date: Wed, 5 Jun 2024 04:19:54 +0000	[thread overview]
Message-ID: <IA1PR20MB560034F0178CB4E3B98C8C3DCEF92@IA1PR20MB5600.namprd20.prod.outlook.com> (raw)

Hello, I am trying to utilize the oci-container-service-type to manage containers in Guix and running into issues. Below is the relevant portion of my config.scm:

(service oci-container-service-type
    (list
      (oci-container-configuration
        (image "pihole/pihole:latest")
        (provision "pihole")
        (network "host")
        (ports
          '("53:53/tcp"
            "53:53/udp"
            "67:67/udp"  ; Only required if using Pi-hole as DHCP server
            "80:80/tcp"))
        (environment
          '(("TZ" . "America/Chicago")))
          ; Uncomment and set a secure password, or it will be random
          ; '(("WEBPASSWORD" . "set a secure password here"))
        (volumes
          '("/docker/Pihole:/etc/pihole"
            "/docker/Dnsmasq:/etc/dnsmasq.d")))))

Below is the error I get when reconfiguring my system:

Backtrace:
In srfi/srfi-1.scm:
   586:29 19 (map1 (#<<service> type: #<service-type agetty 7f965…> …))
   586:29 18 (map1 (#<<service> type: #<service-type syslog 7f965…> …))
   586:29 17 (map1 (#<<service> type: #<service-type console-font…> …))
   586:29 16 (map1 (#<<service> type: #<service-type virtual-term…> …))
   586:29 15 (map1 (#<<service> type: #<service-type x11-socket-d…> …))
   586:29 14 (map1 (#<<service> type: #<service-type ntp 7f965729…> …))
   586:29 13 (map1 (#<<service> type: #<service-type dbus 7f96572…> …))
   586:29 12 (map1 (#<<service> type: #<service-type elogind 7f96…> …))
   586:29 11 (map1 (#<<service> type: #<service-type upower 7f965…> …))
   586:29 10 (map1 (#<<service> type: #<service-type avahi 7f9657…> …))
   586:29  9 (map1 (#<<service> type: #<service-type wpa-supplica…> …))
   586:29  8 (map1 (#<<service> type: #<service-type network-mana…> …))
   586:29  7 (map1 (#<<service> type: #<service-type gdm 7f96575c…> …))
   586:17  6 (map1 (#<<service> type: #<service-type oci-containe…> …))
   586:17  5 (map1 (#<<oci-container-configuration> user: "oci-cont…>))
In gnu/services/docker.scm:
   691:38  4 (oci-container-shepherd-service _)
   631:17  3 (%oci-image-loader "pihole" "pihole/pihole:latest" "pih…")
   599:16  2 (lower-oci-image "pihole" "pihole/pihole:latest")
In ice-9/boot-9.scm:
  1685:16  1 (raise-exception _ #:continuable? _)
  1685:16  0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure struct-vtable: Wrong type argument in position 1 (expecting struct): "pihole/pihole:latest"


I also tried the example config given in the devel Guix manual, however that yielded the same results. Any help would be greatly appreciated.

             reply	other threads:[~2024-06-09 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  4:19 Samuel Willey [this message]
2024-06-09 12:22 ` oci-container-service-type: Wrong type argument in position 1 (expecting struct) Carlo Zancanaro

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=IA1PR20MB560034F0178CB4E3B98C8C3DCEF92@IA1PR20MB5600.namprd20.prod.outlook.com \
    --to=samuelwilley@hotmail.com \
    --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).