Add support for VMDK files

[ManoMarks]

Support for VMDK files should be on our roadmap

[pcgeek86]

This should theoretically be possible, if someone wants to take on this task.

• Option 1: Mount VMDK directly to a folder, using vmware-mount.exe
• Option 2: Convert the VMDK to VHDX format first, then perform discovery

VDisk converter: https://www.starwindsoftware.com/converter Microsoft Virtual Machine Converter: https://www.microsoft.com/en-us/download/details.aspx?id=42497

[pcgeek86]

Here's a document on vmware-mount.exe http://www.vmware.com/pdf/VMwareDiskMount.pdf

[sixeyed]

Alternatively, is there a desire to be able to run this live - against the local machine, or a remote machine? I can see having to take a VM offline as a bit of friction.

On 14 Sep 2016 17:41, "Trevor Sullivan" notifications@github.com wrote:

Here's a document on vmware-mount.exe http://www.vmware.com/pdf/ VMwareDiskMount.pdf

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/docker/communitytools-image2docker-win/issues/2#issuecomment-247075710, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJm5Xh4jDIJvX3JPknxGw7UWatFRIZLks5qqCOjgaJpZM4J79LU .

[ManoMarks]

@pcgeek86 if we used option 1, would it operate any differently? Once mounted, would the rest of discovery be the same?

[pcgeek86]

@sixeyed The design goals for this project were to scan against an offline WIM or VHDX image.

The code could be modified as part of a different project, or through community contributions, to achieve scanning against a remote, "online" (booted up) system.

[pcgeek86]

@ManoMarks Option 1, in theory, would allow the code to operate mostly the same way. Changes to the mounting process would be required, but the discovery itself would remain the same.