Open nikosT opened 2 years ago
Hello,
I can reproduce the error. I will look at it, in the meantime you can use oarsub -C <jobid>
to connect to the job.
Yes, I did and it works. I think the issue has to do with the fact that the way the oar-docker-compose is implemented, the containers do no share the same "file system". So, if a file is created in /home/user1 then it is visible only from the "machine" it was created and NOT all the containers.
I'm running the oar-docker-compose "cluster". After logging via CLI to frontend I submitted successfully an interactive job:
Without closing this CLI, on another CLI, I logged in to the frontend again, then I checked that job is running, however, I get no access to any of the
node1
andnode2
machines viaoarsh
(and by setting theOAR_JOB_ID
env. var.),If I run
oarsh
inside any of the reserved nodes, then I get access, but not through the frontend. Additionally, the job as shown above belongs to the same useruser1
.NODE List is shown below: