build01: building ly7nc2jkf1l30ib4wp3y82npzwf32869-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/tmppaymm94v/ca. ░ Spawning container client on /build/tmppaymm94v/client. ░ Spawning container server on /build/tmppaymm94v/server. <<< NixOS Stage 2 >>> booting system configuration /nix/store/i63h5sq7gln4gw1qbj0k4ywq57spk858-nixos-system-ca-test running activation script... setting up /etc... 2: host0@if4: 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 a2abafaf-365b-4099-9b8f-5163d53aab50' Running as unit: run-p467-i334122.service; invocation ID: a6c8a368d88343e4997381186f967ac6 To attach to container ca run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*a2abafaf-365b-4099-9b8f-5163d53aab50') --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 a2abafaf-365b-4099-9b8f-5163d53aab50 <<< NixOS Stage 2 >>> booting system configuration /nix/store/cf13fxi4h4k8gbc1yplrh9h611fy5zff-nixos-system-client-test running activation script... setting up /etc... 2: host0@if3: 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 fd772f3d-5fa7-4ea8-a3ff-280476df51f1' Running as unit: run-p304-i334129.service; invocation ID: a9bed87e7f63411d95d1757d1f219366 To attach to container client run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*fd772f3d-5fa7-4ea8-a3ff-280476df51f1') --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 fd772f3d-5fa7-4ea8-a3ff-280476df51f1 <<< NixOS Stage 2 >>> booting system configuration /nix/store/5yi8h4cv929dryqx3rk68npqv6xdp41b-nixos-system-server-test running activation script... setting up /etc... 2: host0@if5: 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 11874e01-ec77-485e-a363-04bd2e6bd160' Running as unit: run-p398-i334137.service; invocation ID: 6796b485be2b4bb89556b966bc9198d9 To attach to container server run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*11874e01-ec77-485e-a363-04bd2e6bd160') --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 11874e01-ec77-485e-a363-04bd2e6bd160 + 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): { [1010 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: Nov 2 10:07:54 2026 GMT * expire date: Dec 2 10:07:54 2028 GMT * issuer: CN=minica root ca 075ff4 * 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): { [1010 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: Nov 2 10:07:54 2026 GMT * expire date: Dec 2 10:07:54 2028 GMT * issuer: CN=minica root ca 075ff4 * 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): { [1010 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [110 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: Nov 2 10:07:54 2026 GMT * expire date: Dec 2 10:07:54 2028 GMT * issuer: CN=minica root ca 075ff4 * 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: Nov 2 10:07:07 2026 GMT * expire date: Jan 31 10:08:07 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 45656 % 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: Mon, 02 Nov 2026 10:08:10 GMT < content-type: application/octet-stream < content-length: 20 < content-type: text/plain < { [5 bytes data] 100 20 100 20 0 0 689 0 0 * Connection #0 to host test.foo:443 left intact (finished: waiting for success: curl -v https://test.foo, in 3.19 seconds) + openssl s_client -connect test.foo:443 -servername test.foo + openssl x509 -text -noout Certificate: Data: Version: 3 (0x2) Serial Number: ad:18:02:37:23:83:fc:1c:37:79:53:08:ba:be:5c:4c Signature Algorithm: ecdsa-with-SHA256 Issuer: CN=Clan Intermediate CA Validity Not Before: Nov 2 10:07:07 2026 GMT Not After : Jan 31 10:08:07 2027 GMT Subject: CN=test.foo Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:69:52:70:67:5b:38:37:bb:fc:4b:10:65:6a:9b: 64:ca:8c:8f:fa:22:f1:5d:47:7d:d0:01:60:5f:ba: b2:11:6d:3c:d7:39:d5:ec:d3:c6:cf:50:f7:d8:0e: 64:1a:f6:aa:56:08:ee:55:db:ce:7e:34:56:aa:92: ee:7c:fb:9d:3c 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: 33:03:D0:24:A9:09:04:45:01:3B:7F:79:8F:9C:CC:89:1F:7D:8C:FF 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:45:02:21:00:a0:6f:8a:9f:1a:f2:a1:51:7a:de:76:5c:94: 7a:c4:0f:4e:2b:06:98:31:04:10:48:28:28:e7:ce:2b:d4:ab: 45:02:20:4a:a4:13:a9:03:e4:6b:b8:54:37:5a:a3:eb:44:e2: d6:f9:a3:dd:9a:ff:72:ee:fb:f5:08:70:52:a3:84:92:ff Container ca terminated by signal KILL. Container client terminated by signal KILL. Container server terminated by signal KILL.