Hello.
I'm trying to create new docker vm using community helper script:
Unfortunately, the script freezes on
Some investigation showed me, that it freezes specifically, while executing:
The output of this command while executed within the script (I've modified it to display the output):
Here's the related verbose output of the
Some context on my proxmox instance, that I believe may be helpful.
The SSD is 256GB.
Any ideas ?
I'm trying to create new docker vm using community helper script:
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/vm/docker-vm.sh)"Unfortunately, the script freezes on
Expanding root partition to use full disk spaceSome investigation showed me, that it freezes specifically, while executing:
virt-resize --expand /dev/sda1 ${FILE} expanded.qcow2 >/dev/null 2>&1The output of this command while executed within the script (I've modified it to display the output):
Code:
Expanding root partition to use full disk space
Formatting 'expanded.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=10737418240 lazy_refcounts=off refcount_bits=16
[ 0.0] Examining debian-12-nocloud-amd64.qcow2
**********
Summary of changes:
virt-resize: /dev/sda14: This partition will be left alone.
virt-resize: /dev/sda15: This partition will be left alone.
virt-resize: /dev/sda1: This partition will be resized from 2.9G to 9.9G.
The filesystem ext4 on /dev/sda1 will be expanded using the ‘resize2fs’
method.
**********
[ 7.4] Setting up initial partition table on expanded.qcow2
[ 13.6] Copying /dev/sda14
[ 13.6] Copying /dev/sda15
[ 13.9] Copying /dev/sda1
◓ 95% ⟦▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒═════⟧ 00:00Here's the related verbose output of the
virt-resize command, while executed within the script (it's different % progress, because it's different run)
Code:
[ 17.5] Copying /dev/sda1
guestfsd: => copy_device_to_device (0x126) took 0.29 secs
guestfsd: <= copy_device_to_device (0x126) request length 104 bytes
commandrvf: stdout=n stderr=y flags=0x0
commandrvf: udevadm --debug settle -E /dev/sda1
No filesystem is currently mounted on /sys/fs/cgroup.
Failed to determine unit we run in, ignoring: No data available
commandrvf: stdout=n stderr=y flags=0x0
commandrvf: udevadm --debug settle -E /dev/sdb3
No filesystem is currently mounted on /sys/fs/cgroup.
Failed to determine unit we run in, ignoring: No data available
◐ 80% ⟦▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒════════════════════⟧ 00:02Some context on my proxmox instance, that I believe may be helpful.
The SSD is 256GB.
Code:
root@pve:~# pvesm scan lvm
pve
Code:
root@pve:~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 5 0 wz--n- <237.00g 16.00g
Code:
root@pve:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 1G 0 part /boot/efi
└─sda3 8:3 0 237G 0 part
├─pve-swap 252:0 0 6.7G 0 lvm [SWAP]
├─pve-root 252:1 0 69.6G 0 lvm /
├─pve-data_tmeta 252:2 0 1.4G 0 lvm
│ └─pve-data-tpool 252:4 0 141.8G 0 lvm
│ ├─pve-data 252:5 0 141.8G 1 lvm
│ ├─pve-vm--100--disk--0 252:6 0 32G 0 lvm
│ └─pve-vm--100--disk--1 252:7 0 4M 0 lvm
└─pve-data_tdata 252:3 0 141.8G 0 lvm
└─pve-data-tpool 252:4 0 141.8G 0 lvm
├─pve-data 252:5 0 141.8G 1 lvm
├─pve-vm--100--disk--0 252:6 0 32G 0 lvm
└─pve-vm--100--disk--1 252:7 0 4M 0 lvm
Code:
root@pve:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-aotz-- 141.80g 4.67 1.27
root pve -wi-ao---- <69.57g
swap pve -wi-ao---- 6.73g
vm-100-disk-0 pve Vwi-aotz-- 32.00g data 20.69
vm-100-disk-1 pve Vwi-aotz-- 4.00m data 14.06
Code:
root@pve:~# lvscan
ACTIVE '/dev/pve/data' [141.80 GiB] inherit
ACTIVE '/dev/pve/swap' [6.73 GiB] inherit
ACTIVE '/dev/pve/root' [<69.57 GiB] inherit
ACTIVE '/dev/pve/vm-100-disk-0' [32.00 GiB] inherit
ACTIVE '/dev/pve/vm-100-disk-1' [4.00 MiB] inherit
Code:
root@pve:~# lvdisplay
--- Logical volume ---
LV Name data
VG Name pve
LV UUID 2jda7W-wHcb-cRZl-qh4V-t77z-D5jV-Luscdc
LV Write Access read/write (activated read only)
LV Creation host, time proxmox, 2025-11-28 12:42:50 +0100
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 0
LV Size 141.80 GiB
Allocated pool data 4.67%
Allocated metadata 1.27%
Current LE 36302
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:5
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID LznY6o-jZqu-Sg8x-k8Wo-kSOq-KfbA-C7JS5S
LV Write Access read/write
LV Creation host, time proxmox, 2025-11-28 12:42:50 +0100
LV Status available
# open 1
LV Size 6.73 GiB
Current LE 1723
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0
--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID gvXcmX-pwep-peeq-XFsg-RfOe-TFJD-5UCY5T
LV Write Access read/write
LV Creation host, time proxmox, 2025-11-28 12:42:50 +0100
LV Status available
# open 1
LV Size <69.57 GiB
Current LE 17809
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:1
--- Logical volume ---
LV Path /dev/pve/vm-100-disk-0
LV Name vm-100-disk-0
VG Name pve
LV UUID EYyOmS-1W7n-YZOO-22fl-UDHy-2EWe-mW28bM
LV Write Access read/write
LV Creation host, time pve, 2025-11-28 14:53:41 +0100
LV Pool name data
LV Status available
# open 1
LV Size 32.00 GiB
Mapped size 20.69%
Current LE 8192
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:6
--- Logical volume ---
LV Path /dev/pve/vm-100-disk-1
LV Name vm-100-disk-1
VG Name pve
LV UUID luvWPb-DOBx-YLgD-67pH-IQww-Eiuh-LHliBI
LV Write Access read/write
LV Creation host, time pve, 2025-11-28 14:53:52 +0100
LV Pool name data
LV Status available
# open 1
LV Size 4.00 MiB
Mapped size 14.06%
Current LE 1
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:7Any ideas ?