Just referring to the first step on the github page
` Shut down the docker containers
docker-compose down Before pulling the new file and stuff. I seem to be in the weird situation where the docker stuff is all running (i assume, since the ami seems to be functioning properly and i can access the web ui and stuff) but I don't have the compose file, or at least can't seem to find it in /opt `
Also, I just wanted to say thanks for the tool! I'm managing a small data science practice and it's going to be really nice to have a view of all of the experiments we've got and know our GPU utilization, all without having to give every data scientist access to each box where the workflows are run. Incredibly stoked.
♥ ❤ ♥
I don't have the compose file, or at least can't seem to find it in
/opt
you can manually take down all dockers with:docker psthen docker stop <container id> for each container id
Not intentional! When I launched the AMI it was running an older version
I think this is exactly the reason they decided to change the location 🙂 so you will have to manually upgrade, reasoning is we changed directory names (maybe a few more things)
Yes shutdown the current docker copse curl the new docker compose rename folder spin it up againFull instructions here:
https://allegro.ai/clearml/docs/docs/deploying_clearml/clearml_server_aws_ec2_ami.html#upgrading
Hi ShallowArcticwolf27
However, the AMI for version 0.16.1 has the following docker-compose file
I think we moved the docker-compose yaml when we upgraded from trains to clearml. Any reason your are installing the old docker-compose ?
Not intentional! When I launched the AMI it was running an older version of the trains software, so I just want the old docker file to shut all that stuff down so i can pull and compose the new docker stuff.
If that's not necessary and I can just kill all the current docker stuff running in the AMI and pull the new stuff i'm happy to do that!
Right on, looks like I'm upgraded now! Thanks again.