Marketplace container-management
Create, manage, and optimize LXC containers in Proxmox. Control container lifecycle, manage resources, and coordinate container deployments across nodes.
install
source · Clone the upstream repo
git clone https://github.com/aiskillstore/marketplace
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/dataknifeai/container-management" ~/.claude/skills/aiskillstore-marketplace-container-management && rm -rf "$T"
manifest:
skills/dataknifeai/container-management/SKILL.mdsource content
Container Management Skill
Create, manage, and optimize LXC containers in your Proxmox environment.
What this skill does
This skill enables you to:
- List containers on specific nodes
- Get detailed container configuration and status
- Start, stop, reboot, and delete containers
- Create new LXC containers with basic or advanced configuration
- Clone existing containers
- Modify container resource allocation
- Monitor container performance metrics
- Manage container templates
- Plan container deployment strategies
- Optimize resource allocation for containers
When to use this skill
Use this skill when you need to:
- Check container status and configuration
- Manage container lifecycle (start/stop/reboot)
- Monitor container performance and resource usage
- Adjust container resources (CPU, memory, storage)
- Create new containers
- Troubleshoot container issues
- Plan container migrations
- Optimize container placement
- Manage container templates
Available Tools
- List all containers on a specific nodeget_containers
- Get detailed container status and configurationget_container_status
- Get full container configuration detailsget_container_config
- Start a containerstart_container
- Stop a container immediatelystop_container
- Gracefully shutdown a containershutdown_container
- Reboot a containerreboot_container
- Create a new LXC container with basic configurationcreate_container
- Create a container with advanced configuration optionscreate_container_advanced
- Clone an existing containerclone_container
- Delete a containerdelete_container
Typical Workflows
Container Lifecycle Management
- Use
to list available containersget_containers - Use
orget_container_status
to check stateget_container_config - Use start/stop/reboot to manage container operations
- Monitor container health during changes
Container Creation & Deployment
- Use
orcreate_container
to provision new containercreate_container_advanced - Use
to verify configurationget_container_status - Use
to create copies for testing or deploymentclone_container - Use
to review detailed settingsget_container_config - Document container details for reference
Container Lifecycle Operations
- Use
for graceful shutdownshutdown_container - Use
to restart containerreboot_container - Use
for immediate termination if neededstop_container - Monitor container status during transitions
Container Troubleshooting
- Use
to diagnose issuesget_container_status - Use reboot/restart to recover from problems
- Use snapshots to rollback problematic changes
- Analyze logs and metrics for root cause
Example Questions
- "List all containers on the worker node"
- "What's the status and resource usage of container 101?"
- "Get the full configuration of container 105"
- "Start the database container"
- "Create a new container with 2 cores and 4GB RAM"
- "Clone container 102 to create a test environment"
- "Gracefully shutdown container 103"
- "Delete container 199 and remove all data"
- "Show me all containers and their resource allocation"
Response Format
When using this skill, I provide:
- Container listings with status and resources
- Detailed container configuration and metrics
- Status confirmations for container operations
- Resource utilization analysis
- Optimization recommendations
Best Practices
- Monitor container performance regularly
- Use cloning for quick container deployment
- Create containers with appropriate resource allocation
- Use graceful shutdown to minimize disruption
- Plan resource allocation carefully
- Balance containers across nodes
- Implement monitoring for critical containers
- Use container templates for consistency
- Document container configuration and purpose
- Test changes in development first
- Monitor disk usage and resource limits
- Clean up unused containers regularly
- Use meaningful hostnames for easy identification