DreamCompute instances are created with a specified SSH key which is used for gaining initial access. This guide covers some basic steps to attempt to retrieve the data, and gain access again if desired.
Things to keep in mind
IP addresses will change
To get back into an instance requires re-creating it. The new instance receives new IPv4 and IPv6 addresses.
Know your instance type
One can generally find out if an instance uses an ephemeral or volume boot disk by looking at the 'Instances' page of the dashboard and seeing if the name of a custom image or an operating system is listed in the 'Image Name' column. If one is listed, the instance is ephemeral. If one isn't, it uses a volume boot disk.
Regain access to ephemeral instance
- Navigate to the Instances page of the DreamCompute dashboard.
- To the right of the instance, click the Create Snapshot button and give the snapshot a name. This creates an operating system image of your running instance. Please wait for this process to complete before moving on to the next step (generally it doesn't take more than a few minutes).
- Make note of the flavor of the instance, the name of the instance, and any other features that should be retained in the new instance.
- Click the Launch Instance button to create a new instance. On the "Source" tab, set "Select Boot Source" to "Instance Snapshot" and click the up arrow symbol next to the name of the snapshot created in the previous step. Please note that you cannot create a new volume from instance snapshots in DreamCompute, so make sure to set "Create New Volume" to "No".
- On the 'Key Pair' tab, select the Key Pair to be used for the default user. If there are no valid keys available, you can use the Create Key Pair or Import Key Pair buttons to associate a new key pair with your project (and this instance). When you're done customizing the instance, click the Launch button on the bottom right.
- Once the new instance has booted, attempt to log into it with the default username and the new IP address.
- If everything looks correct and access has been restored, the original instance can now be deleted.