Unraid Custom ISO about windows

[Reziem]

Yes that is because you named the file custom.ISO and not custom.iso. On Linux files are case-sensitive, so it cannot find the file. On Windows it doesnt matter if you use upper or lowercase.

Ah weird, never noticed that. good catch, not sure why it was like that. Sorry about that haha.

[Reziem]

I really appreciate your help with this and being patient with my lack of attention to detail. This docker container is sweet and I have some cool ideas / use cases for this :) Thank you again

[Fsystem]

@Fsystem It can happen if the automatic install XML tries to select an edition that does not exist in the custom ISO. If you follow the steps for manual installation in the FAQ, you can workaround this.

OK,My custom.iso is win81 enterprise. manual installation failed. So I replaced with win81 pro. It works

[kroese]

What files do you have in /mnt/disk1/docker-virtuals/WindowsinDocker/ ?

If for example there is a data.qcow2 with Win10 installed, it will boot off this harddrive instead of the DVD with the custom ISO. So in that case you can solve it by deleting data.qcow2.

[Reziem]

What files do you have in /mnt/disk1/docker-virtuals/WindowsinDocker/ ?

If for example there is a data.qcow2 with Win10 installed, it will boot off this harddrive instead of the DVD with the custom ISO. So in that case you can solve it by deleting data.qcow2.

Here is what is in mnt/disk1/docker-virtuals/WindowsinDocker/

Sweet I'll try deleting that file.

[kroese]

The harddisk has higher boot priority than the optical drive, so you should delete data.qcow2 and win10x64.iso and keep only custom.img and then it should work.

I will create a new version of the container soon which will work easier for custom images, because I can understand the way it works now is confusing.

[Reziem]

The harddisk has higher boot priority than the optical drive, so you should delete data.qcow2 and win10x64.iso and keep only custom.img and then it should work.

I deleted those two files and it still appears to be downloading win10x64

I will create a new version of the container soon which will work easier for custom images, because I can understand the way it works now is confusing.

No worries, I appreciate it. That will be very nice :)

[kroese]

Yes that is because you named the file custom.ISO and not custom.iso. On Linux files are case-sensitive, so it cannot find the file. On Windows it doesnt matter if you use upper or lowercase.

[Reziem]

Dang it, sorry one more thing. Is this a permissions issue maybe?

[Reziem]

Never mind. I think I got it now. :)

A little odd it says custom.iso.iso but regardless it seems to be working.

[kroese]

No it's not a permission issue.. If it does not list any editions it means none qualify for installation. Did you enter a product key before that screen? Because in that case it might have something to do with the key not being valid.

[Fsystem]

Dang it, sorry one more thing. Is this a permissions issue maybe?

How did you solve this problem? I encountered the same issue when running this docker image on my VMware Debian vm.

[kroese]

@Fsystem It can happen if the automatic install XML tries to select an edition that does not exist in the custom ISO. If you follow the steps for manual installation in the FAQ, you can workaround this.