Powershell installing msi

Asked Jun 22 '18 at 12:29

Active Jun 22 '18 at 12:39

Viewed 884 times

I am using docker with powershell. I want to download and install webdeploy .msi

I am using the following code:

RUN Invoke-WebRequest http://download.microsoft.com/download/0/1/D/01DC28EA-638C-4A22-A57B-4CEF97755C6C/WebDeploy_x86_en-US.msi  -OutFile webdeploy.msi; \
Start-Process msiexec -Wait -ArgumentList /q, /i, -PassThru, webdeploy.msi ; \
Remove-Item -Force webdeploy.msi

When I run: docker build -t test.

Everything goes fine.

When I then check the folder "Program Files (x86)" inside the container I dont see any folder "IIS".

I also tried:

RUN Invoke-WebRequest http://download.microsoft.com/download/0/1/D/01DC28EA-638C-4A22-A57B-4CEF97755C6C/WebDeploy_x86_en-US.msi -OutFile webdeploy.msi; \
Start-Process msiexec -Wait -ArgumentList /q, /i, webdeploy.msi ; \
Remove-Item -Force webdeploy.msi

Some help would be appreciated.

edited Jun 22 '18 at 12:39

asked Jun 22 '18 at 12:29

xxx2017

1

First, what is the purpose of the backslashes at the end of the lines? Second, I don't think -Passthru is a valid MSI parameter. – EBGreen Jun 22 '18 at 12:32
I tried with and without. Doesnt make any difference. – xxx2017 Jun 22 '18 at 12:40
With and without the backslashes, or the -Passthru, or both? – EBGreen Jun 22 '18 at 12:40
both Also I used backslashes for installing nodeJS .msi and that works fine. – xxx2017 Jun 22 '18 at 12:43
first, unless docker requires the backslashes for some reason, remove them. Second try this: `-ArgumentList '/i webdeploy.msi /q'` – EBGreen Jun 22 '18 at 12:46
Tried it but I still dont see anything installed in the container. – xxx2017 Jun 22 '18 at 13:18
Add logging to the install. – EBGreen Jun 22 '18 at 13:20
How do I add logging to the install? – xxx2017 Jun 22 '18 at 13:21
At any command prompt type `msiexec /?` – EBGreen Jun 22 '18 at 13:22
So I write Start-Process msiexec /? -Wait -ArgumentList '/i webdeploy.msi /q' ; \ ? – xxx2017 Jun 22 '18 at 13:24
No you do what I said. You open a command prompt and type `msiexec /?` Then you read the help message to learn how to add logging to the install. – EBGreen Jun 22 '18 at 13:26
What's the base image? WOW64 is now an optional component, which if not enabled should break things further. – Lex Li Jun 22 '18 at 21:11
The logging helped. It seemed that it failed because of x86 version. When I changed it to x64 installation worked fine. – xxx2017 Jun 25 '18 at 07:57

Powershell installing msi

0 Answers0

Linked