Missing SCONE_CAS_ADDR is causing the `scone-print-arg-env` demo to fail

[st3iny]

I tried to follow this tutorial and spotted a minor flaw in the screencast for Task 2-D.

The final step to run the ./scone-print-arg-env binary inside the crosscompilers image fails because it tries to resolve an invalid (default?) CAS address cas..

It works fine when I set SCONE_CAS_ADDR=scone-cas.cf manually.

Error

bash-5.1# SCONE_CONFIG_ID=$SESSION/scone-print-arg-env ./scone-print-arg-env
[SCONE|FATAL] tools/starter/main.c:603:enclave_create(): Could not create enclave builder: Unable to resolve address for cas
Caused by: no record found for Query { name: Name("cas."), query_type: AAAA, query_class: IN }

Works when specifing the address of CAS

bash-5.1# SCONE_CONFIG_ID=$SESSION/scone-print-arg-env SCONE_CAS_ADDR=scone-cas.cf ./scone-print-arg-env
[SCONE|WARN] src/enclave/dispatch.c:136:print_runtime_info(): Application runs in SGX debug mode. Its memory can be read from outside the enclave with a debugger! This is not secure!
[SCONE|WARN] scone_rrt::implementation::eai rust-crates/scone_rrt/src/implementation/eai.rs:246:Unable to connect to LAS at default 'las' address (Resolution of LAS address las:18766 failed)- enclave won't be able to attest itself
[SCONE|WARN] src/syscall/syscall.c:31:__scone_ni_syscall(): system call: membarrier, number 324 is not supported
[SCONE|WARN] src/process/init.c:415:__scone_apply_secure_config(): Ignoring `SCONE_PWD` environment variable and host provided process working directory.
        Applying process working directory from service's session configuration (/)
argv: ./scone-print-arg-env arg1 arg2 arg3
environ:
SCONE_MODE=auto
env3=enclave
env1=running
env2=in