Martin.B

Thanks @talajasi7 I was able to verify the issue. The main reason is not specifying `--queue` which causes the agent to look for a queue with the `default` tag, since...

Hi @majdzr > When I restart the machine, the agents disappear and I need to recreate them. You mean how to spin the agent automatically every reboot? If this is...

I think there was a commit fixing this issue, basically conda found the incorrect torch on the "default" channel, and then the pip fallback kicked in (resulting in the download,...

Thanks @Deams51 ! That is a great idea, and I think it relates to more than just the Linux install, I guess it would apply to any AMI/GCP image as...

Hi @bzamecnik > but probably needs a restart when adding new users or changing passwords. Yes this is correct. That said restarting the server will have no effect on running...

Hi @sagyHarpaz From the error codes all dockers are not running, and it seems like there is an issue with the docker service for windows setup (not specifically the trains-server...

Hi @Mikehem , Since **trains-server** is pre-configured for unrestricted CORS origins, the most likely reason for this error is the **trains-apiserver** component not responding to any request, usually due to...

Hi @agarwalchaitanya, The easiest way would be to convert the `docker-compose.yml` to `heroku.yml` - they're both quite similar (see [here](https://devcenter.heroku.com/articles/build-docker-images-heroku-yml)) From there, it's just a matter of deploying the `heroku.yml`....

Hi @SiftingSands Sure, I can't see any real reason it should not work. We will be more than happy to support if you run into any issues, and once you...

Hi @ranrubin The original bug (#49) is actually a bug in *Trains* (even though the manifestation is in the trains-server) . The bug is, *Trains* will try to create links...