I found the reason for these kinds of problems. The reason is that the execution service inside the docker cannot correctly access the input files as well as the output files.
One can fix this problem by changing ``` INPUT_FILE_URL_PREFIX = "http://localhost:6789/fixtures/functions/ordered_set_intersect/"; OUTPUT_FILE_URL_PREFIX = "http://localhost:6789/fixtures/functions/ordered_set_intersect/"; ``` to ``` INPUT_FILE_URL_PREFIX = "http://teaclave-file-service:6789/fixtures/functions/ordered_set_intersect/"; OUTPUT_FILE_URL_PREFIX = "http://teaclave-file-service:6789/fixtures/functions/ordered_set_intersect/"; ``` The domain name "teaclave-file-service" can be found via `$ docker ps` you can get the domain name for teaclave file service under the "NAMES" column like this: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES XXXXXXXX python:3 "./scripts/simple_ht…" 1 days ago Up 1 days - teaclave-file-service Note that in a real-world case, the url or the input files should be provided by the user. In the built-in example, the developer embeds those files for test usage and we may use our own files here. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/458#issuecomment-763192282
