build01: building bsjl9ps46n916jlrdqizhaimvpxri8y0-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 <<< NixOS Stage 2 >>> booting system configuration /nix/store/hh37lrn4bs8q75ivx0i2krr6k0l7v35z-nixos-system-ca-test running activation script... setting up /etc... 2: host0@if5: 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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo 0882965b-7cbe-4b8f-b6cc-9386e977d92e' Running as unit: run-p469-i31317759.service; invocation ID: 1d29495812f54768b40c24746c66d34a To attach to container ca run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*0882965b-7cbe-4b8f-b6cc-9386e977d92e') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 0882965b-7cbe-4b8f-b6cc-9386e977d92e <<< NixOS Stage 2 >>> booting system configuration /nix/store/z95lfjp0h7m28dbr2sykrljgakgmgf3l-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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo 8ae44293-a00c-406a-9f0f-8c3158c5d79d' Running as unit: run-p304-i31317762.service; invocation ID: 0ea1d6fd9f1645f88371e03a3c3f9ff5 To attach to container client run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*8ae44293-a00c-406a-9f0f-8c3158c5d79d') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 8ae44293-a00c-406a-9f0f-8c3158c5d79d <<< NixOS Stage 2 >>> booting system configuration /nix/store/zrhs3dm022fca0bai4iv9mr8psypyfik-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.4 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/fl0k50cdb33a5xxzlzmz5782yw66rj4r-coreutils-9.11/bin/sleep 999999999 && echo 6aa007ad-cea5-4cc7-92ff-01e26efb2c38' Running as unit: run-p398-i31317770.service; invocation ID: 320b90d14ecd4f5f9e4878a8ae551441 To attach to container server run on the same machine that runs the test: sudo nsenter --user --target $(\pgrep -f '^/bin/sh.*6aa007ad-cea5-4cc7-92ff-01e26efb2c38') --mount --uts --ipc --net --pid --cgroup /bin/sh -c bash To inject external network and continue test, run: sudo /nix/store/76jq0mngg7m8zv5yjz1qgg0xspzi8x2w-python3-3.13.15/bin/python3.13 /nix/store/1v002aslhnn1b7kr1fq8m14lldran2b0-test-driver-0.0.1/lib/python3.13/site-packages/test_driver/inject_network.py 6aa007ad-cea5-4cc7-92ff-01e26efb2c38 + 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): { [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 4 15:44:25 2026 GMT * expire date: Nov 3 15:44:25 2028 GMT * issuer: CN=minica root ca 28ca49 * 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): { [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 4 15:44:25 2026 GMT * expire date: Nov 3 15:44:25 2028 GMT * issuer: CN=minica root ca 28ca49 * 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): { [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 4 15:44:25 2026 GMT * expire date: Nov 3 15:44:25 2028 GMT * issuer: CN=minica root ca 28ca49 * 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): { [930 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 4 15:43:39 2026 GMT * expire date: Jan 2 15:44:39 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 55958 % 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] * 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] { [5 bytes data] 100 20 100 20 0 0 665 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: f6:95:0a:dc:dc:a0:e4:4e:6a:54:03:e9:41:54:d1:59 Signature Algorithm: ecdsa-with-SHA256 Issuer: CN=Clan Intermediate CA Validity Not Before: Oct 4 15:43:39 2026 GMT Not After : Jan 2 15:44:39 2027 GMT Subject: CN=test.foo Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (256 bit) pub: 04:98:72:87:44:48:58:8e:8e:f0:34:43:c3:3d:58: 2d:9b:12:01:eb:27:e7:a5:0f:44:b3:5f:cc:51:64: a3:ca:49:a6:55:30:b5:d0:f1:a3:e6:3c:80:b5:f1: 5a:b7:94:62:cb:2f:31:f9:7c:40:e2:ba:01:44:60: 1e:39:6b:50:dc 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: 82:41:F8:23:42:A2:C9:5B:9B:B1:08:FB:3C:74:68:3D:CA:DE:B9:22 X509v3 Authority Key Identifier: 12:7B:BB:87:0A:DE:A2:A4:61:95:C5:6B:DF:BC:AA:93:FE:C3:16:9F 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:44:02:20:68:66:3c:d3:50:bc:ec:b9:af:15:21:b6:d3:11: b7:9c:5d:56:f0:d7:44:5e:2c:c0:85:62:05:b1:71:b3:2c:d9: 02:20:3a:0d:9b:25:11:56:e0:fe:50:ba:9e:98:bc:b5:fb:33: b1:39:dd:44:05:b0:a7:52:1c:83:c4:2f:67:e5:7b:71