Delete a container
Stop a workload and remove the resource from active Console management.
Delete a container when you no longer need it. This stops the connected workload and marks the RDC resource as deleted. There is no restore action in the Console.
Before you begin
Export application data you need to retain, record necessary configuration, and check whether clients still use the container. For imported containers, deletion also stops the connected workload; it is not just removal of a Console shortcut.
Do not use this action as evidence that every underlying image or storage volume has been physically erased. It does not provide a storage-erasure guarantee.
Delete the resource
- Open the container and select Danger Zone.
- Select Delete container.
- Review the confirmation and select Confirm deletion.
- After the Console returns to the list, confirm that the resource is no longer listed as active.
You do not need to apply pending configuration or wait for a restarting workload to become healthy before requesting deletion. Unsaved settings and other Console settings requests do not disable Danger Zone. Deletion still requires permission and confirmation, and duplicate deletion requests are blocked while one is pending.
If an active resource operation conflicts with deletion or the connected workload cannot be stopped, the API returns an error. The confirmation stays open so you can retry after resolving the error; a failed request does not remove the resource from the Console.
Remove custom DNS records you no longer need from your DNS provider separately. If you only need a temporary shutdown, use Stop instead.
Passkey confirmation for deletion
If your account has a registered passkey, deleting this cloud resource requires a new passkey verification, even if you already verified your sign-in. After confirming deletion in Console, use Verify with passkey in the RDC Account window. Allow pop-ups for Console if the verification window is blocked.
The verification applies only to the selected resource and one deletion attempt. Cancelling, closing the window, or letting the request expire does not send the deletion request. If deletion fails, start a new attempt and verify again. Accounts without a registered passkey continue to use the existing deletion confirmation. Your resource deletion permission is still required.