Hi CheerfulGorilla72
the "installed packages" section is used as "requirements.txt for the agent.
Are you saying the autodetection fails to detect all packages? You can specify in "manual execution" (i.e not when the agent is running the code), to just take the requirements.txt locally:` Task.force_requirements_env_freeze(requirements_file="./requirements.txt")
notice the above call should be executed Before Task.init
task = Task.init(...) `3. If you clear all the "installed packages" section in the UI, the agent will revert to using requirements.txt from the git repository itself.
wdyt?
great, point 2 sounds like the right thing!)
please tell me, is it possible to somehow make it so that costomous fakets, which are not in the public domain, would be used?
for example, if I somehow start the execution of an agent task in a specific docker container?)
Thank you very much for your help and for such a convenient product!)
I haven't figured out the alents yet, but it already looks amazing!)
for example, if I somehow start the execution of an agent task in a specific docker container?)
You mean to specify the container from code? or to make sure the agent can access private docker container registry ? Or is it for private pypi container repository ?
-
specify container from UI
-
libraries in the ubuntu repository have not yet reached their pip / pypi repository
In the UI you can edit the base container image + add "SETUP SHELL SCRIPT", with any missing "apt update && apt-get install -y ..."