starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Docker-VM Script fails when using Linstor as storage type. #2096

New Issue
Closed
opened 2026-02-05 03:44:32 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 03:44:32 +03:00
Owner
Copy Link

Originally created by @sbcrumb on GitHub (Nov 30, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

docker-vm.sh

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/docker-vm.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

When running the docker-vm.sh script on a Proxmox node that uses LINSTOR as a storage backend, the script fails during VM disk creation.

The disk image is downloaded and expanded successfully, but the script aborts when Proxmox attempts to attach the VM disk via the LINSTOR Proxmox storage plugin.

LINSTOR returns:

HTTP 404 – resource definition not found

"vm-300-disk-1" is missing from the LINSTOR database

Proxmox then fails the qm set command with exit code 255

The failure does not occur when using non-LINSTOR storage (e.g., local-lvm or ZFS).
This suggests the script assumes Proxmox will auto-create LINSTOR disk resources, but the LINSTOR plugin requires resource definitions to be created first.

🔄 Steps to reproduce the issue.

Step 1: Use a Proxmox node with LINSTOR configured as a storage backend.
Step 2: Run the docker-vm.sh script with default settings.
Step 3: Select a LINSTOR storage (e.g., linstor-storage or linstor-storage2) when prompted for VM disk storage.
Step 4: Script downloads and expands the cloud image successfully.
Step 5: Script fails when attaching scsi0 / efidisk0 using qm set and LINSTOR storage.

❌ Paste the full error output (if available).

✔️ Expanded image to full size
Creating a Docker VM
API Return-Code: 404. Message: Could not create diskless resource vm-300-disk-1 on prox1, because:
[{"ret_code":-4611686018407202515,"message":"Resource definition 'vm-300-disk-1' not found.",
"cause":"The specified resource definition 'vm-300-disk-1' could not be found in the database",
"details":"Node: prox1, Resource: 'vm-300-disk-1'",
"correction":"Create a resource definition with the name 'vm-300-disk-1' first."}]
at /usr/share/perl5/PVE/Storage/Custom/LINSTORPlugin.pm line 569.

[ERROR] in line 526: exit code 255: while executing command
qm set $VMID -efidisk0 ${DISK0_REF}${FORMAT} -scsi0 ${DISK1_REF},${DISK_CACHE}${THIN}size=${DISK_SIZE} -boot order=scsi0 -serial0 socket > /dev/null

🖼️ Additional context (optional).

The issue only happens when selecting LINSTOR storage in the script.
The VM creates successfully when using any non-LINSTOR storage.
linstor resource-definition list confirms that vm-300-disk-1 is never created.
The LINSTOR Proxmox plugin expects Proxmox to create a resource definition before activating the diskless resource, which the script does not handle.

Originally created by @sbcrumb on GitHub (Nov 30, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? docker-vm.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/docker-vm.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. When running the docker-vm.sh script on a Proxmox node that uses LINSTOR as a storage backend, the script fails during VM disk creation. The disk image is downloaded and expanded successfully, but the script aborts when Proxmox attempts to attach the VM disk via the LINSTOR Proxmox storage plugin. LINSTOR returns: HTTP 404 – resource definition not found "vm-300-disk-1" is missing from the LINSTOR database Proxmox then fails the qm set command with exit code 255 The failure does not occur when using non-LINSTOR storage (e.g., local-lvm or ZFS). This suggests the script assumes Proxmox will auto-create LINSTOR disk resources, but the LINSTOR plugin requires resource definitions to be created first. ### 🔄 Steps to reproduce the issue. Step 1: Use a Proxmox node with LINSTOR configured as a storage backend. Step 2: Run the docker-vm.sh script with default settings. Step 3: Select a LINSTOR storage (e.g., linstor-storage or linstor-storage2) when prompted for VM disk storage. Step 4: Script downloads and expands the cloud image successfully. Step 5: Script fails when attaching scsi0 / efidisk0 using qm set and LINSTOR storage. ### ❌ Paste the full error output (if available). ✔️ Expanded image to full size Creating a Docker VM API Return-Code: 404. Message: Could not create diskless resource vm-300-disk-1 on prox1, because: [{"ret_code":-4611686018407202515,"message":"Resource definition 'vm-300-disk-1' not found.", "cause":"The specified resource definition 'vm-300-disk-1' could not be found in the database", "details":"Node: prox1, Resource: 'vm-300-disk-1'", "correction":"Create a resource definition with the name 'vm-300-disk-1' first."}] at /usr/share/perl5/PVE/Storage/Custom/LINSTORPlugin.pm line 569. [ERROR] in line 526: exit code 255: while executing command qm set $VMID -efidisk0 ${DISK0_REF}${FORMAT} -scsi0 ${DISK1_REF},${DISK_CACHE}${THIN}size=${DISK_SIZE} -boot order=scsi0 -serial0 socket > /dev/null ### 🖼️ Additional context (optional). The issue only happens when selecting LINSTOR storage in the script. The VM creates successfully when using any non-LINSTOR storage. linstor resource-definition list confirms that vm-300-disk-1 is never created. The LINSTOR Proxmox plugin expects Proxmox to create a resource definition before activating the diskless resource, which the script does not handle.
OVERLORD added the bug label 2026-02-05 03:44:32 +03:00
OVERLORD commented 2026-02-05 03:44:35 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 30, 2025):

Never used and heard of this storage. Without Testing Nobody can try it. So i think this should be solved by Community as PR

@MickLesk commented on GitHub (Nov 30, 2025): Never used and heard of this storage. Without Testing Nobody can try it. So i think this should be solved by Community as PR
OVERLORD commented 2026-02-05 03:44:44 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 30, 2025):

Never used and heard of this storage. Without Testing Nobody can try it. So i think this should be solved by Community as PR

@MickLesk commented on GitHub (Nov 30, 2025): Never used and heard of this storage. Without Testing Nobody can try it. So i think this should be solved by Community as PR
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2096
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?