- Home
- Skills
- DevOps & Cloud
- Cold Start: Fix Proxmox LXC Containers That Won't Behave
More screenshots
Works with the AI Agents you already use
Cold Start: Fix Proxmox LXC Containers That Won't Behave
An independent review checked them against the Proxmox documentation and source code, and we corrected a claim about clone MAC addresses that turned out to be wrong.
$5
Cold Start: Fix Proxmox LXC Containers That Won't Behave
Example session with this skill installed
New Ubuntu 24.04 LXC on Proxmox. apt update sat for ten minutes and then printed Temporary failure resolving archive.ubuntu.com. The host runs Tailscale. /etc/resolv.conf in the container shows nameserver 100.100.100.100. I ran pct set 121 --nameserver 1.1.1.1 and checked resolv.conf again and it's unchanged. After this I want Tailscale inside the container too.
- Read your context and instructions
- Compiled the cold start
Summary
Your pct set worked. It changed the container's config, but a running container keeps its old DNS file until you restart it. One restart will apply the DNS change and the Tailscale device settings together.
The cause
The container copied the host's DNS file when you created it. Tailscale had pointed that file at an address the container can't reach, so apt hung and then failed to resolve. Tailscale inside an unprivileged container also needs a device it doesn't have yet.
What the answer covers
- Set DNS so this can't recur.
- Add the Tailscale prerequisites.
- Confirm DNS, then join the tailnet.
- Avoid two traps that catch people on the next container and on clones.
The skill gives your agent the commands in order.
Connects securely to your tools. The creator never sees your data.
About this skill
These problems look like something else, which is why they take hours.
Your agent fixes
apthanging for ten minutes because the container inherited MagicDNSpct set --nameserverthat appears to do nothing- Tailscale failing in an unprivileged container
- A restored guest fighting the original for its DHCP lease
- A clone showing up as the same Tailscale node
- One container freezing the whole host through swap on a ZFS zvol
- RAM sizing for AI models, so a model load can't take every guest down
How it was tested
Each fix comes from running a Proxmox estate. An independent review checked them against the Proxmox documentation and source code, and we corrected a claim about clone MAC addresses that turned out to be wrong.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Written for current Proxmox VE. Some older versions need the config file lines it lists.
Memory sizing rules are a safe starting point. Measure your own model.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
- Software
- Proxmox VE with shell access
Permissions
File Scopes
The skill asks before stopping, rebooting or removing swap on a live host.