pct restore --password option does not set root password (works with pct create)

[nethub]

Hi all,

When restoring a container from a vzdump backup using pct restore, the --password option does not set the root password in the restored container.

The same --password option works correctly when used with pct create.

Is this a known limitation or a bug?

Proxmox VE version: 9.1.1
Container: unprivileged , AlmaLinux 9, Ubuntu 24

Steps to reproduce​

1. backup a container:
   

   vzdump 101 --mode stop --compress zstd --dumpdir /var/lib/vz/dump/

   
   
2. Restore the backup to a new CT and assign a root password:
   

   pct restore 102 /var/lib/vz/dump/vzdump-lxc-101-2025_12_18-14_56_55.tar.zst \
     --password $PASSWORD \
     --unprivileged 1 \
     --rootfs local-lvm:10

   
   
3. Start the restored container:
   

   pct start 102

   
   
4. Attempt to log in as root

---

Expected behavior​

The root password of CT 102 should be set to the value provided via --password

---

Actual behavior​

• Root password remains unchanged from the backup
• The password provided via --password is ignored
• No warning or error is shown during restore

 

[fabian]

the password is only handled when creating a new container, but this could also be extended to work when restoring. could you file an issue in our bugzilla? https://bugzilla.proxmox.com/show_bug.cgi?id=7158 is tangentially related..

 

[nethub]

Thank you, Fabian. I followed the documentation here:
https://pve.proxmox.com/pve-docs/pct.1.html

Based on the documentation, I expected the --password option to be able to assign the root password during pct restore.

I have submitted this issue to Bugzilla for tracking, thanks a lot:
https://bugzilla.proxmox.com/show_bug.cgi?id=7164

 

[fabian]

yes. restore and create share a common API endpoint, and in this case, --password is currently only handled for create. it should either error out or be supported when set via restore.

 

[nethub]

Hi fabian,

We noticed that this issue does not seem to be fixed yet. Could we please check if there are any updates or a planned fix for this?

 

[fabian]

nobody picked up working on it yet..