Update CLOUD_SETUP.md
Tell people that the secure cloud option for RunPod.io no longer works, and they must use the community cloud.
This commit is contained in:
parent
45f41289db
commit
d999c2fc1c
|
@ -4,6 +4,8 @@
|
|||
|
||||
Click here -> [EveryDream2 template](https://runpod.io/gsc?template=d1v63jb36t&ref=bbp9dh8x) to load a fully configured Docker image. Both Tensorboard and Jupyter lab are automatically started for you and you can simply click the links to connect.
|
||||
|
||||
**IMPORTANT**: This will only work on the Community Cloud, not the Secure Cloud!
|
||||
|
||||
If you wish to sign up for Runpod, please consider using this [referral link](https://runpod.io?ref=oko38cd0) to help support the project. 2% of your spend is given back in the form of credits back to the project and costs you nothing.
|
||||
|
||||
You can also [enable full SSH support](https://www.runpod.io/blog/how-to-achieve-true-ssh-on-runpod) by setting the PUBLIC_KEY environment variable
|
||||
|
@ -54,4 +56,4 @@ Make sure to delete the instance when you are done. Runpod and Vast use a trash
|
|||
|
||||
The Docker container should enable running on any host that supports using Docker containers, including GCP or AWS, and potentially with lifecycle management services such as GKE and ECS.
|
||||
|
||||
Most people looking to use GCP or AWS will likely already understand how to manage instances, but as a warning, make sure you know how to manage the instance lifecycles so you don't end up with a surprise bill at the end of the month. Leaving an instance running all month can get expensive!
|
||||
Most people looking to use GCP or AWS will likely already understand how to manage instances, but as a warning, make sure you know how to manage the instance lifecycles so you don't end up with a surprise bill at the end of the month. Leaving an instance running all month can get expensive!
|
||||
|
|
Loading…
Reference in New Issue