[GH-ISSUE #10716] Allow update-lxcs.sh to skip stopped containers #2307

Closed
opened 2026-02-26 12:51:59 +03:00 by kerem · 0 comments
Owner

Originally created by @enboig on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10716

Originally assigned to: @michelroegl-brunner on GitHub.

🌟 Briefly describe the feature

Have a flag to skip stopped containers when updating.

📝 Detailed description

I would like a flag so when updating LXC with cron, the ones which are stopped aren't. Sometimes I have them stopped because I broke something and I want to check later, so I prefer them being untouched.

💡 Why is this useful?

If a LXC is stopped there could be a reason behind to keep it stopped; having it started and stopped may cause undesired effects.

Originally created by @enboig on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10716 Originally assigned to: @michelroegl-brunner on GitHub. ### 🌟 Briefly describe the feature Have a flag to skip stopped containers when updating. ### 📝 Detailed description I would like a flag so when updating LXC with cron, the ones which are stopped aren't. Sometimes I have them stopped because I broke something and I want to check later, so I prefer them being untouched. ### 💡 Why is this useful? If a LXC is stopped there could be a reason behind to keep it stopped; having it started and stopped may cause undesired effects.
kerem 2026-02-26 12:51:59 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2307
No description provided.