Thank you for your reply AgitatedDove14 ; I found the option in
clearml.conf ; we will use it for now 🙂 .
But a warning instead of an error would be good. Maybe a bit of a context for our use case: we use clearml-task to create components of a pipeline, we only create tasks and do not schedule them for the execution (so that the pipeline does it instead), so we do not expect the paths for the data storage to be available then. Does this sound like a reasonable workflow, or is there a better way maybe?
It verifies it has access to it when actually creating the Task, maybe it should be a warning?!
fyi: you can also change the value from the UI (under Execution output) or have a default one set in the
clearml.conf used by the agent