[Bug] unable to restore CT xxx - ERROR: archive contains no configuration file - pegaprox-latest-lxc-amd64.tar.xz

[PaPaTheGMan]

Hey there! 👋 Thanks for taking the time to report this bug — we appreciate it!

Please keep in mind: PegaProx is developed and maintained entirely by volunteers in our free time. We do our best, but we can't work magic 🪄 — please be patient, we'll get to your issue as soon as we can.

Want to help keep PegaProx alive?

• ⭐ Star the project — it's free and helps a lot!
• 💖 Become a Sponsor — helps us dedicate more time to development
• 🤝 Contributing code or docs is always welcome too!

---

Describe the bug

As the title indicates, am unable to create a new LXC Container from downloaded image.

Steps to Reproduce

1. Download image from Website - "https://github.com/PegaProx/project-pegaprox/releases/latest/download/pegaprox-latest-lxc-amd64.tar.xz"
2. Run "pct restore 105 /var/lib/vz/template/cache/pegaprox-latest-lxc-amd64.tar.xz --
   storage local-lv" from Proxmox root shell
3. Receive "unable to restore CT 105 - ERROR: archive contains no configuration file"

Expected behavior

Install should proceed without error.

Environment

• PegaProx Version:
• Installation Method:
• OS:
• Browser:
• Behind Reverse Proxy?
• UI?

Logs

Screenshots

Checklist

• I have searched existing issues to make sure this is not a duplicate
• I am using the latest version of PegaProx

[mkellermann97]

Thanks — and this one's on us, not you. The LXC asset (pegaprox-latest-lxc-amd64.tar.xz) is a rootfs template, but our deploy doc tells you to pct restore it — and pct restore only accepts vzdump backups (which carry the CT config), so it correctly errors with "archive contains no configuration file." Stopgap that works today: treat it as a template — pct create 105 local:vztmpl/pegaprox-latest-lxc-amd64.tar.xz --storage local-lvm --hostname pegaprox --memory 2048 --cores 2 --net0 name=eth0,bridge=vmbr0,ip=dhcp (or in the PVE UI: CT Templates → it's already in the cache → Create CT and pick it). I'm flagging the doc + the asset so the documented command matches what we actually ship. Appreciate the precise repro — opencollective.com/pegaprox keeps the fixes coming. — Marcus

[PaPaTheGMan]

Thanks for the quick response. I used your suggestion and the container seemed to load just fine. I did get a warning - “WARN: Systemd 257 detected. You may need to enable nesting”but it did start without complaint. Just one question, please, what are the login credentials? I tried root - PegaProx2026! and pegaprox_admin - PegaProx2026!. Neither worked Thanks, Greg Blum From: mkellermann97 ***@***.***> Sent: Tuesday, June 30, 2026 1:11 PM To: PegaProx/project-pegaprox ***@***.***> Cc: PaPaTheGMan ***@***.***>; Author ***@***.***> Subject: Re: [PegaProx/project-pegaprox] [Bug] unable to restore CT xxx - ERROR: archive contains no configuration file - pegaprox-latest-lxc-amd64.tar.xz (Issue #599) [https://avatars.githubusercontent.com/u/257130705?s=20&v=4]mkellermann97 left a comment (PegaProx/project-pegaprox#599)<#599 (comment)> Thanks - and this one's on us, not you. The LXC asset (pegaprox-latest-lxc-amd64.tar.xz) is a rootfs template, but our deploy doc tells you to pct restore it - and pct restore only accepts vzdump backups (which carry the CT config), so it correctly errors with "archive contains no configuration file." Stopgap that works today: treat it as a template - pct create 105 local:vztmpl/pegaprox-latest-lxc-amd64.tar.xz --storage local-lvm --hostname pegaprox --memory 2048 --cores 2 --net0 name=eth0,bridge=vmbr0,ip=dhcp (or in the PVE UI: CT Templates → it's already in the cache → Create CT and pick it). I'm flagging the doc + the asset so the documented command matches what we actually ship. Appreciate the precise repro - opencollective.com/pegaprox keeps the fixes coming. - Marcus - Reply to this email directly, view it on GitHub<#599?email_source=notifications&email_token=ANTUBLDOX22RU3OFZAOSSB35CPYCLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBUGYYDONJXGAZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4846075703>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANTUBLGOEFZOQYLF7O3PPBT5CPYCLAVCNFSNUABGKJSXA33TNF2G64TZHMYTCMZWGYYDSNRVGU5US43TOVSTWNBXG44DGNZUGE3TRILWAI>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/ANTUBLGTO6373Z4QOLIFEQD5CPYCLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBUGYYDONJXGAZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/ANTUBLG2PUBYWX7442MDQAD5CPYCLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBUGYYDONJXGAZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[mkellermann97]

Quick follow-up: the docs are now corrected and live — https://docs.pegaprox.com/getting-started/deploy-premade/ shows the proper pct create (CT template) and qm importdisk (VM qcow2) steps instead of the old pct restore/qmrestore. Thanks again for catching it. — Marcus

[mkellermann97]

Resolved — the deploy docs are corrected and live: https://docs.pegaprox.com/getting-started/deploy-premade/ now shows pct create (CT template) and qm importdisk (VM qcow2) instead of the old pct restore. Thanks again for the precise repro. — Marcus