Title
#tech-support
Esraa Madi

Esraa Madi

11/14/2022, 11:39 AM
Hi everyone, I launched Argilla sever (screenshot from logs below), and the web page keeps loading (image below) then I investigated the network section and found a blocking error (the error is attached below). I searched a bit about it, and they talked about the conflict between HTTPS and HTTP protocols and need to request the domain owner to add HTTPS as well
Rick Lamers

Rick Lamers

11/14/2022, 12:47 PM
It looks like Argilla isn't configured to be fronted by an HTTPS proxy that is talking to it over HTTP. Based on reading the Argilla docs it looks like it should be feasible to run it as a service in Orchest, but it might require tweaking of the configuration of their container image. Are you using
argilla/argilla-server
for the service?
Esraa Madi

Esraa Madi

11/14/2022, 12:49 PM
Yes
Rick Lamers

Rick Lamers

11/14/2022, 1:14 PM
I must say generally it's not recommended to run complex services like Argilla that depend on other container services like Elasticsearch as an Orchest service. It's better to run them on platforms like Heroku, Railway, DigitalOcean or Northflank and communicate with them from your Orchest context/pipelines. That said, I'm trying to create an example for you that successfully runs ES + Argilla so you have a minimal working example to reference
9:29 AM
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
9:31 AM
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.
Esraa Madi

Esraa Madi

11/15/2022, 10:36 AM
Thanks Rick for your support
Rick Lamers

Rick Lamers

11/15/2022, 2:46 PM
You ask interesting questions 🤓. Happy to help!