Skip to content

fix: clarify consequences of canister delete #303

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
raymondk merged 1 commit into from
Jun 25, 2026
Merged

fix: clarify consequences of canister delete #303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/guides/canister-management/lifecycle.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,6 +264,8 @@ This is useful during development when you want a clean slate. The canister ID i

Deleting permanently removes a canister from the network. The canister ID cannot be reused.

> Note: Canisters are like real estate on the IC. Creating them costs cycles. Instead of deleting a canister, consider reusing it in a different project. Check the [cli reference](https://cli.internetcomputer.org/1.0/concepts/project-model/#canister-ids) for more information.

1. Stop the canister first:

```bash
Expand All @@ -276,7 +278,7 @@ icp canister stop my-canister -e ic
icp canister delete my-canister -e ic
```

Remaining cycles are refunded to the controller who made the delete request.
> **Warning** The remaining cycles in the canister are lost, see [github issue](https://github.com/dfinity/icp-cli/issues/431).

## Migrate a canister between subnets

Expand Down
Loading