From: Markus Ebner via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Markus Ebner <info@ebner-markus.de>
Subject: [pve-devel] [PATCH container 0/1] Fix #6989: cloudinit: Enable joliet ISO extension for config disks
Date: Mon, 3 Nov 2025 12:38:20 +0100 [thread overview]
Message-ID: <mailman.528.1762178392.362.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 3368 bytes --]
From: Markus Ebner <info@ebner-markus.de>
To: pve-devel@lists.proxmox.com
Cc: Markus Ebner <info@ebner-markus.de>
Subject: [PATCH container 0/1] Fix #6989: cloudinit: Enable joliet ISO extension for config disks
Date: Mon, 3 Nov 2025 12:38:20 +0100
Message-ID: <20251103113900.140922-1-info@ebner-markus.de>
The nocloud ISO image disk format mandates 4 files in the root folder
called "network-config", "user-data", "meta-data" and "vendor-data".
These filenames are not ISO9660 Level 3 compatible.
To circumvent this, Proxmox - to date - generates nocloud cloud-init
ISOs with the Rockridge extension (-R) - which adds support for POSIX
compatible filenames and metadata. But the Rockridge extension is not
supported by Windows. In order to also support these filenames for
Windows, also add the joliet extension to generated ISO disks.
Signed-off-by: Markus Ebner <info@ebner-markus.de>
Markus Ebner (1):
fix #6989: cloudinit: Enable joliet ISO extension for config disks
src/PVE/QemuServer/Cloudinit.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.51.1
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-11-03 13:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.528.1762178392.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=info@ebner-markus.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.