Open MarkRx opened 3 months ago
Looks like I can workaround this by setting AZURE_DEVOPS_CACHE_DIR
to a bogus volume that the execution user has write access to. code
ok.
you are welcome to open a PR to update the documentation with this trick if you think its necessary https://pr-agent-docs.codium.ai/installation/azure/#azure-devops-webhook
In a locked down container environment (a security practice where all files are read only within a container and only volumes can be written to) a server fails to boot due to an ADO error even when not using ADO. It appears to be because ADO attempts to write
./azure-devops
on during initialization.line
Fix could be to enhance the delayed exception handling to handle any exception then rethrow it here