but I still had time to go inside the container, export the PATH variables for my poetry and python versions, and run the poetry install command there

You can theoretically do that in the docker init bash script that will be executed before the task is cloned and run

How do you explain that it works when I ssh-ed into the same AWS container instance from the autoscaler?

I tried too. I do not have more logs inside the ClearML agent 😞

Using a pyenv virtual env then exporting LOCALPYTHON env var

Yes should be correct. Inside the bash script of the task.

@<1523701070390366208:profile|CostlyOstrich36> poetry is installed as part of the bash script of the task.

The init script of the AWS autoscaler only contains three export variables I set.

Because I was ssh-ing to it before the fail. When poetry fails, it installs everything using PIP

When the task finally failed, I was kicked of from the container

Yes, the problem is it's still really hidden (the error, I mean)

My issue has been resolved going with pip.

where did you specify it?

The same container

Yes same error

I am currently trying with a new dummy repo and I iterate over the dependencies of the pyproject.toml.

and are you sure these are the same env vars available when the agent does the same?

It just allows me to have access to poetry and python installed on hte container

or just to the AWS instance?

@<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?

@<1556812486840160256:profile|SuccessfulRaven86> , to make things easier to debug, can you try running the agent locally?

@<1556812486840160256:profile|SuccessfulRaven86> can you try with -vvv instead of -v ?

Yes indeed, but what about the possibility to do the clone/poetry installation ourself in the init bash script of the task?

How is it still up is the task failed?

the autoscaler always uses docker mode

And I just tried with Python 3.8 (default version of the image) and it still fails.

Poetry Enabled: Ignoring requested python packages, using repository poetry lock file!
Creating virtualenv debug in /root/.clearml/venvs-builds/3.8/task_repository/clearmldebug.git/.venv
Using virtualenv: /root/.clearml/venvs-builds/3.8/task_repository/clearmldebug.git/.venv
2023-04-18 15:03:52
Installing dependencies from lock file
Finding the necessary packages for the current system
Package operations: 6 installs, 0 updates, 0 removals
failed installing poetry requirements: Command '['poetry', 'install', '-n', '-v']' returned non-zero exit status 1.

The autoscaler just runs it on an AWS instance, inside a docker container - there's no difference from running it yourself inside a docker container - did you try running it inside a docker container as well?

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

How to make sure that the python version is correct?

I see it's running inside 3.9, so I assume it's correct

@<1523701070390366208:profile|CostlyOstrich36> @<1523701087100473344:profile|SuccessfulKoala55> I tried with dummy repo. Using Python and stripe packages ONLY in the pyproject.toml

Here is my result (still failing) :

Poetry Enabled: Ignoring requested python packages, using repository poetry lock file!
Creating virtualenv debug in /root/.clearml/venvs-builds/3.9/task_repository/clearmldebug.git/.venv
Using virtualenv: /root/.clearml/venvs-builds/3.9/task_repository/clearmldebug.git/.venv
Installing dependencies from lock file
Finding the necessary packages for the current system
Package operations: 6 installs, 0 updates, 0 removals
failed installing poetry requirements: Command '['poetry', 'install', '-n', '-v']' returned non-zero exit status 1.
Ignoring pip: markers 'python_version >= "3.10"' don't match your environment