Skip to content

Fill gaps from assistant conversations: pod shutdown and MCP volumes - #796

Open
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/cbfad5ea
Open

Fill gaps from assistant conversations: pod shutdown and MCP volumes#796
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/cbfad5ea

Conversation

@mintlify

@mintlify mintlify Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Address two recurring assistant conversation gaps: users trying to stop a Pod with Linux shutdown and users asking how to attach a network volume when creating a Pod via the MCP server.

Changes

  • pods/manage-pods.mdx: add a warning to the Stop a Pod section explaining that shutdown, poweroff, and halt do not stop a Pod (containers, not VMs) and pointing to runpodctl pod stop $RUNPOD_POD_ID from inside the Pod.
  • get-started/mcp-servers.mdx: add a second pod-creation example that includes Network Volume ID and Volume Mount Path, and note that the MCP server forwards these to the REST API's networkVolumeId / volumeMountPath fields on POST /pods.

Context

Assistant query buckets in the last week showed a thumbs-down thread on "can I use shutdown inside a pod?" and repeated MCP-server questions about attaching a network volume at pod creation.

@mintlify

mintlify Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
runpod-docs 🟢 Ready View Preview Aug 17, 2026, 1:12 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants