Coming back to this, I think the issue is that Argilla does not support running on a subpath (e.g. http://somedomain.app.com/argilla-service/). To enable this usually applications either include all resources relatively or allow you to configure a ‘base url’ config option. In this case, Argilla’s frontend is requesting resources with absolute paths referencing the root (e.g.

/_nuxt/8d9ab4d.js

instead of

/argilla/service/_nuxt/8d9ab4d.js

. If you’re keen on running Argilla in Orchest that kind of ‘base url’ ability of the application is required. I recommend reaching out to the folks of Argilla at https://github.com/argilla-io/argilla/issues

P.S. I got Elastic to run using the following service command/args: command:

sh

args:

-c 'echo "discovery.type: single-node" >> /usr/share/elasticsearch/config/elasticsearch.yml && cat /usr/share/elasticsearch/config/elasticsearch.yml && /usr/local/bin/docker-entrypoint.sh'

This uses the elasticsearch.yml to configure it in single-node. That avoids their awkward use of environment variables with a period in it. How nonstandard that is is confirmed by a basic shell command:

sh -c 'discovery.type=single node echo 1'

throws an error because

sh

does not allow environment variables to have periods.

Posted here: https://github.com/argilla-io/argilla/issues/1899#issuecomment-1315046534