build01: building ywkmqqdqp9shlh7bg86mpmsszr5hz82z-container-test-run-certificates.drv additionally exposed symbols: ca, client, server, start_all, machines, driver, Machine, wait_for_signal Starting ca Starting client Starting server ░ Spawning container ca on /build/tmplcnlr1cb/ca. ░ Spawning container client on /build/tmplcnlr1cb/client. ░ Spawning container server on /build/tmplcnlr1cb/server. <<< NixOS Stage 2 >>> booting system configuration /nix/store/bm104wbaldfsyjz985497b4gdy3f7xdx-nixos-system-ca-test running activation script... setting up /etc... 2: host0@if3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:06:76:42:a9:8d brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 260.5 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo 4fbc1826-c3b4-407b-8eb9-9a6de2f981a5' Running as unit: run-p467-i4419562.service; invocation ID: a82cf61e55f140618d86f36fd0adc95c To attach to container ca run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*4fbc1826-c3b4-407b-8eb9-9a6de2f981a5') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 4fbc1826-c3b4-407b-8eb9-9a6de2f981a5 <<< NixOS Stage 2 >>> booting system configuration /nix/store/cvdwm2mz99kmkcfkh44xxkvfmnh6qviq-nixos-system-client-test running activation script... setting up /etc... 2: host0@if5: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 2a:42:35:28:b1:2f brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 260.5 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo 787d2a52-8bf7-4f59-8ac3-e0ce9f3ff542' Running as unit: run-p304-i4419565.service; invocation ID: f8afd3ffd9624d3ba82bba2ceac5289a To attach to container client run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*787d2a52-8bf7-4f59-8ac3-e0ce9f3ff542') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 787d2a52-8bf7-4f59-8ac3-e0ce9f3ff542 <<< NixOS Stage 2 >>> booting system configuration /nix/store/pkqsf62imcnpssmm7nc9fxl9fazq9fj7-nixos-system-server-test running activation script... setting up /etc... 2: host0@if4: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether be:aa:dd:39:86:e7 brd ff:ff:ff:ff:ff:ff link-netnsid 0 setting up age secrets... starting systemd... systemd 260.5 running in system mode (+PAM +AUDIT -SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON +UTMP +LIBARCHIVE) Detected virtualization systemd-nspawn. Detected architecture arm64. Detected first boot. Initializing machine ID from container UUID. Applying preset policy. Populated /etc with preset unit settings. Queued start job for default target Multi-User System. <<< Welcome to NixOS test (aarch64) - console >>> + systemd-run /bin/sh -c '/nix/store/3l7ygqcc6v0rbi9d4j1m6phi6sz86j98-coreutils-9.11/bin/sleep 999999999 && echo 7961546b-c445-4058-9531-0f28e7115958' Running as unit: run-p399-i4419569.service; invocation ID: 31c86ad6787b4271a80626419a37910f To attach to container server run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*7961546b-c445-4058-9531-0f28e7115958') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/q1khrhbn506imjxx7kiqcbihycawa6kl-python3-3.13.15/bin/python3.13 /nix/store/6kasz8qw4mw4szwg29sxyra6pgbwz4zq-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 7961546b-c445-4058-9531-0f28e7115958 + systemctl restart acme-order-renew-ca.foo.service + systemctl restart acme-test.foo.service client: waiting for success: curl -v https://test.foo + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [1008 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [112 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Oct 27 10:06:19 2026 GMT * expire date: Nov 26 10:06:19 2028 GMT * issuer: CN=minica root ca 5dcd6c * Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 13 * SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) * closing connection #0 curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the webpage mentioned above. + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [1008 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [112 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Oct 27 10:06:19 2026 GMT * expire date: Nov 26 10:06:19 2028 GMT * issuer: CN=minica root ca 5dcd6c * Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 13 * SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) * closing connection #0 curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the webpage mentioned above. + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [1008 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [111 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Oct 27 10:06:19 2026 GMT * expire date: Nov 26 10:06:19 2028 GMT * issuer: CN=minica root ca 5dcd6c * Certificate level 0: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * Certificate level 1: Public key type EC/secp384r1 (384/192 Bits/secBits), signed using ecdsa-with-SHA384 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 13 * SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) * closing connection #0 curl: (60) SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19) More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the webpage mentioned above. + curl -v https://test.foo * Host test.foo:443 was resolved. * IPv6: (none) * IPv4: 192.168.1.3 * Trying 192.168.1.3:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [1552 bytes data] * SSL Trust Anchors: * OpenSSL default paths (fallback) { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [1210 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [931 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [78 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [52 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [52 bytes data] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / id-ecPublicKey * ALPN: server accepted h2 * Server certificate: * subject: CN=test.foo * start date: Oct 27 10:05:33 2026 GMT * expire date: Jan 25 10:06:33 2027 GMT * issuer: CN=Clan Intermediate CA * Certificate level 0: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256 * Certificate level 1: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256 * Certificate level 2: Public key type EC/prime256v1 (256/128 Bits/secBits), signed using ecdsa-with-SHA256 * subjectAltName: "test.foo" matches cert's "test.foo" * OpenSSL verify result: 0 * SSL certificate verified via OpenSSL. * Established connection to test.foo (192.168.1.3 port 443) from 192.168.1.2 port 48932 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 0* using HTTP/2 * [HTTP/2] [1] OPENED stream for https://test.foo/ * [HTTP/2] [1] [:method: GET] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: test.foo] * [HTTP/2] [1] [:path: /] * [HTTP/2] [1] [user-agent: curl/8.22.0] * [HTTP/2] [1] [accept: */*] } [5 bytes data] > GET / HTTP/2 > Host: test.foo > User-Agent: curl/8.22.0 > Accept: */* > * Request completely sent off } [5 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [265 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [265 bytes data] < HTTP/2 200 < server: nginx < date: Tue, 27 Oct 2026 10:06:35 GMT < content-type: application/octet-stream < content-length: 20 < content-type: text/plain < { [5 bytes data] 100 20 100 20 0 0 699 0 0 * Connection #0 to host test.foo:443 left intact (finished: waiting for success: curl -v https://test.foo, in 3.18 seconds) + openssl s_client -connect test.foo:443 -servername test.foo + openssl x509 -text -noout Certificate: Data: Version: 3 (0x2) Serial Number: 46:d7:a6:f8:52:dc:7b:87:df:28:dd:ea:8d:78:92:82 Signature Algorithm: ecdsa-with-SHA256 Issuer: CN=Clan Intermediate CA Validity Not Before: Oct 27 10:05:33 2026 GMT Not After : Jan 25 10:06:33 2027 GMT Subject: CN=test.foo Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:60:83:70:5d:0c:71:b5:1b:d9:3c:3d:ee:84:9c: 18:53:e7:21:38:f7:97:f3:c6:74:9a:74:f9:4e:93: 49:ca:59:9b:8d:40:6e:9e:50:d3:fd:44:d3:98:3d: 89:b7:9d:8c:94:49:30:e4:ec:59:52:1a:42:8e:cc: e5:42:7c:a7:55 ASN1 OID: prime256v1 NIST CURVE: P-256 X509v3 extensions: X509v3 Key Usage: critical Digital Signature X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Subject Key Identifier: DC:A2:BD:56:A8:A6:EA:0F:9A:CD:8A:C9:E7:FE:90:39:7C:21:96:E2 X509v3 Authority Key Identifier: AF:3D:FB:7F:3A:E2:22:0C:FC:17:43:CF:2B:14:28:42:1E:EC:D0:EF X509v3 Subject Alternative Name: DNS:test.foo 1.3.6.1.4.1.37476.9000.64.1: 0......acme.. Signature Algorithm: ecdsa-with-SHA256 Signature Value: 30:45:02:21:00:9a:99:8e:1c:02:7d:dc:3c:7a:9e:e7:73:dc: 1e:bf:18:1f:f4:5c:7d:18:9b:68:7b:a7:af:21:f1:d7:43:44: 8c:02:20:1d:73:0f:83:0e:9c:99:62:8a:9d:32:e1:8e:df:24: 84:8c:e4:d9:e5:a9:9c:57:3d:cd:db:be:6d:62:e9:8c:c7 Container ca terminated by signal KILL. Container client terminated by signal KILL. Container server terminated by signal KILL.