@harveysanders thanks for reporting!
The error here is misleading for sure, the reason here is that “no such file or directory” is an error string originating from your program, instead of from docker-explorer ls. If docker-explorer ls was successfully executed, its output would include the capital N when a directory isn’t found.
Definitely has to be a way to make the tester more friendly here… Maybe by testing ls on a known directory first before testing the invalid directory case. Will see what we can do!