Yes I take the export statements from my bash script of the task
It just allows me to have access to poetry and python installed on hte container
I think you should try to manually start such a docker container and try to see what fails in the process. Attaching to an existing one has too many differences already
I also did that in the following way:
- I put a sleep inside the bash script
- I ssh-ed to the fresh container and did all commands myself (cloning, installation) and again it worked...
@<1523701087100473344:profile|SuccessfulKoala55> Do you think it is possible to ask to run docker mode in the aws autoscaler, and add the cloning and installation inside the init bash script of the task?
the autoscaler always uses docker mode
Yes indeed, but what about the possibility to do the clone/poetry installation ourself in the init bash script of the task?
I guess it makes no sense because of the steps a clearml-agent works...
I also thought about going to pip
mode but not all packages are detected from our poetry.lock file unfortunately so cannot do that.
You can theoretically do that in the docker init bash script that will be executed before the task is cloned and run
My issue has been resolved going with pip.