PAW installation error unable to copy docker images final step of installation

[Firefly007]

Hello All,

Something went wrong at step 'Installing/Updating IBM Planning Analytics Docker images'
re-exec error: exit status 1: output: Failed to safefile.OpenRelative failed in Win32: open \\?\E:\Docker\windowsfi
lter\8f85628b2b671db3a32536c92d73dc4f2152f9e3f1376839684f306695ee5ed4\Files: Access is denied. (0x1f) Files


I checked following.
1. No antivirus running
2. Firewalls disabled.
3. Started Power shell as administrator.


Would need advise if any one has seen this issue earlier

[Ajay]

Are you installing on a VM or Bare Metal server ? And are you upgrading or doing a fresh install ?


I had a similar issue when upgrading from v54 to v60 a few weeks ago on a VM and I end up blowing away the %programdata% Docker folder to start it.

It was as if something was holding on the \windowsfilter folder.

Assuming that all permissions etc etc are all OK ?

Ajay

[Firefly007]

Hello Ajay,

I did clean up the Programdata/docker still no luck. I get same message.

did you install on OS drive itself or did you try to point to different drive in deamon.jason?


Regards,
Firefly

[gtonkin]

I have had similar issues on older versions of PAW and my notes have:

To clear out all the Windows filter and other docker folders:
Stop PAW then stop the Docker Service. Once done, run the below command.

Download: https://github.com/jhowardmsft/docker-ci-zap
PS> docker-ci-zap.exe -folder "c:\ProgramData\docker"

Not sure how you cleaned out but the zap above does a good job.

[Ajay]

Hello Ajay,

I did clean up the Programdata/docker still no luck. I get same message.

did you install on OS drive itself or did you try to point to different drive in deamon.jason?


Regards,
Firefly

In terms of the VM, we only had a C: and D:
We left the PA Servers on D: and left Docker on C:

On our physical environments (DEV, PREPROD and PROD), we root the containers onto another drive on our Docker servers.

I would also second Gtonkin's comments, that it is very difficult to remove %programdata%\Docker folder without using the Docker zap utility, and that you need to stop PAW and the Docker service before hand.

Once zapped, restart the Docker service and carry on with your PAW start up.

Something else to check is whether the Antivirus is stopping the start up of your containers. Check that the virtual network card for Docker is not being held back

HTH
Ajay

[Firefly007]

I cleaned up container ,volumes and windows filter with scripts from paw folder which comes with Paw installation folder.

I was able to clean up docker folder and Delete docker folder.
recreated docker/cofig folders and pointed config to E:Drive.

restarted paw installation
on windows filter folder i get access denied issue..

[Ajay]

In Powershell (as ADMIN), what happens when you run

docker ps -a

Do you see any containers ?

If you do, are you able to remove them (once you've stopped PAW) ?

[Firefly007]

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
NAMES

no containers

[Ajay]

OK, so what I did next, when this happened to me was:

1. Stopped the "Docker Engine" service
2. I then had to remove the Windows related files. Note, I couldn't do this fully via Windows because the WindowsFilter folder was being held, so I used the utility that Gtonkin mentioned above
3. This took about 20mins
4. Started the "Docker Engine" service
5. Commence PAW installation, using ./Start.ps1

When I did the above it worked for me.

Hope this helps. I didn't do anything else but the steps above.

Perhaps after step 3, a restart of Windows might help, just make sure your "Docker Engine" service is set to "manual" before you reboot, so at least you can see what's going on

Ajay

[Ajay]

recreated docker/cofig folders and pointed config to E:Drive.

Depending on the version of PAW you were on, and where you're going to, I remembered that there was a change to the contents of the daemon.json file

For PAW 2.0.53 or lower, I remember it being like this:

{
"graph": "e:\\Docker_Containers"
}


and then it changed to this:

{
"data-root": "e:\\Docker_Containers"
}