build01: building ci1p4a8mzi8nynqi7fhavir0ijbyf8ic-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/tmpcbgn17lh/ca. ░ Spawning container server on /build/tmpcbgn17lh/server. ░ Spawning container client on /build/tmpcbgn17lh/client. <<< NixOS Stage 2 >>> booting system configuration /nix/store/dgb4rh54p9idm7yygv7v67qdd910ymfa-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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo feb4e986-5908-42b9-9cac-6297e78b57b8' Running as unit: run-p400-i12457064.service; invocation ID: 1b33c6e117164f4eaa46a006d920f4a2 To attach to container ca run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*feb4e986-5908-42b9-9cac-6297e78b57b8') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py feb4e986-5908-42b9-9cac-6297e78b57b8 <<< NixOS Stage 2 >>> booting system configuration /nix/store/38fnyp9clipswfks1s7jhq3wy4aw5v93-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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 780d3db3-b21c-41f3-b533-86a3c259b2ac' Running as unit: run-p304-i12457075.service; invocation ID: 1185151b962142d18132a89b635fd951 To attach to container client run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*780d3db3-b21c-41f3-b533-86a3c259b2ac') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 780d3db3-b21c-41f3-b533-86a3c259b2ac <<< NixOS Stage 2 >>> booting system configuration /nix/store/x6x422id83vyy7d7f03qkqqhqlgp3lal-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/f2jmqpvrz2d2m3iw9i9zjkggh4na5jcs-coreutils-9.11/bin/sleep 999999999 && echo 417aaa89-a57c-404b-92d4-4fd541c57013' Running as unit: run-p363-i12457098.service; invocation ID: 7e0b5430941d4be7a83089f89e7bdae3 To attach to container server run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*417aaa89-a57c-404b-92d4-4fd541c57013') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/vilynzly1pyhawy04ljmrp7n9ffr24qy-python3-3.13.17/bin/python3.13 /nix/store/n7n0z60amrdw29gw8wzyhkxwd9ibcjs3-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 417aaa89-a57c-404b-92d4-4fd541c57013 + 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): { [1009 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 29 00:17:54 2026 GMT * expire date: Nov 28 00:17:54 2028 GMT * issuer: CN=minica root ca 05412a * 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): { [1009 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 29 00:17:54 2026 GMT * expire date: Nov 28 00:17:54 2028 GMT * issuer: CN=minica root ca 05412a * 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): { [1009 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 29 00:17:54 2026 GMT * expire date: Nov 28 00:17:54 2028 GMT * issuer: CN=minica root ca 05412a * 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): { [1009 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 29 00:17:54 2026 GMT * expire date: Nov 28 00:17:54 2028 GMT * issuer: CN=minica root ca 05412a * 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): { [80 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 29 00:17:08 2026 GMT * expire date: Jan 27 00:18:08 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 32822 % 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.23.0] * [HTTP/2] [1] [accept: */*] } [5 bytes data] > GET / HTTP/2 > Host: test.foo > User-Agent: curl/8.23.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: Thu, 29 Oct 2026 00:18:12 GMT < content-type: application/octet-stream < content-length: 20 < content-type: text/plain < { [5 bytes data] 100 20 100 20 0 0 846 0 0 * Connection #0 to host test.foo:443 left intact (finished: waiting for success: curl -v https://test.foo, in 4.21 seconds) + openssl s_client -connect test.foo:443 -servername test.foo + openssl x509 -text -noout Certificate: Data: Version: 3 (0x2) Serial Number: 2c:28:d4:a6:c3:50:51:2b:69:68:08:e2:a9:43:2c:d5 Signature Algorithm: ecdsa-with-SHA256 Issuer: CN=Clan Intermediate CA Validity Not Before: Oct 29 00:17:08 2026 GMT Not After : Jan 27 00:18:08 2027 GMT Subject: CN=test.foo Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:ee:3c:56:0e:7b:00:f7:64:79:63:29:64:fc:77: 63:db:d3:89:ce:0e:5f:e6:48:07:dc:04:36:ec:79: 78:f3:7a:a5:41:70:c6:81:7c:da:0d:80:e7:e8:62: 61:4d:40:71:1a:71:58:9b:58:70:20:44:59:8f:8e: cf:78:32:88:04 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: 80:CB:23:8B:D1:2B:27:EB:96:E7:E9:F1:18:B0:68:B1:F8:2F:4F:25 X509v3 Authority Key Identifier: 2B:A2:2D:4D:6B:EA:4F:AC:70:25:B6:86:D5:10:DA:13:B8:00:B8:1F 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:46:02:21:00:a3:39:b8:a5:25:62:41:c1:7b:e9:0d:e8:2b: 8a:d5:1b:7d:a8:a7:ec:57:58:5f:74:18:5e:d4:2a:99:62:33: e1:02:21:00:9d:f4:58:83:b7:02:c8:64:59:07:37:3b:f6:72: d2:8f:2c:4b:d1:f4:06:67:41:e9:43:ea:3e:35:0b:60:6d:bf Container ca terminated by signal KILL. Container client terminated by signal KILL. Container server terminated by signal KILL.