Skip to content

FAQGuidesChangelogShow & Tell

Loading…

Pod stuck in "starting" for 15 hours after resume

Questions / Help pods

37 views · 1 like · 2 users

Destroying the pod does not destroy the volume — volumes are separate. You can attach it to a new pod afterwards.

Related topics

Rails 8 solid_queue on Larkhost: one pod or two?1 reply
Node.js app memory climbs until OOM — only on Larkhost2 replies
Pods can now be cordoned before a deploy3 replies
How to retrieve boot diagnostics for a destroyed pod?0 replies
Show & Tell: a tiny job runner on pods that sleep between jobs2 replies
Laravel queues stop processing after a deploy1 reply

Suggested topics

How to retrieve boot diagnostics for a destroyed pod?0 replies
Pod restarts by itself 1–3 minutes after waking from idle1 reply
New pods that mount a secret as a file are destroyed within one second2 replies
Pods can now be cordoned before a deploy3 replies
The back porch: what are you running on a single shared-cpu pod?3 replies

One pod has been in starting since yesterday. lark pod stop times out. Is it safe to destroy it, or will that lose the volume?