Hi MysteriousBee56 .

What trains-agent version are you running? Do you run it docker mode (e.g.
trains-agent daemon --queue <your queue name> --docker?

Hi TimelyPenguin76 , My version is 0.15.2rc0 and I am running with this command; trains-agent daemon --detached --gpus 0 --queue default --docker nvidia/cuda --foreground

Can you share the logs from the run?

fatal: destination path '/home/dogukan/.trains/vcs-cache/pre-post-script-repo.git.35f82b395021c8e6afef186fafa662cc/pre-post-script-repo.git' already exists and is not an empty directory. Repository cloning failed: Command '['clone', 'git@192.168.1.230:dogukan/pre-post-script-repo.git', '/home/dogukan/.trains/vcs-cache/pre-post-script-repo.git.35f82b395021c8e6afef186fafa662cc/pre-post-script-repo.git', '--quiet', '--recursive']' returned non-zero exit status 128. Cannot find output file

fatal: destination path '/home/dogukan/.trains/vcs-cache/pre-post-script-repo.git.35f82b395021c8e6afef186fafa662cc/pre-post-script-repo.git' already exists and is not an empty directory.Actually, the error occurs because of this line. I run my experiment firstly on docker, then it creates a folder in the vcs-cache that gives access permission only to root. Then, I run my experiment on venv and it cannot access this folder and cannot create new one because of the same name.

If I delete this folder that is in ~/.trains/vcs-cache directory, it fixes the problem

Yap, this should solve the issue. Let me check the causing of it

Hi MysteriousBee56 ,
Yes this is permissions issue, the docker creates all folders as root (as it is the root user running inside the docker), Then when you execute in venv mode, you are running it from your user, which obviously cannot change root created folders.

So, is there any trick to fix this issue?

MysteriousBee56
Well we don't want to ask sudo permission automatically, and usually setups do no change, but you can diffidently call this one before running the agent 😉
sudo chmod 777 -R ~/.trains/