IBM Support

Container is marked for removal and cannot be started - Driver "windowsfilter" failed to remove root filesystem: hcsshim::GetComputerSystems

Troubleshooting


Problem

When Planning Analytics Workspace containers are starting up , the following errors occur:
Error: for <container_name>  Cannot start service monitor: container is marked for removal and cannot be started.
Or
Exception occurred:
Execution failed with exit code 1:
ERROR: for <container_name> <GUID>:
driver "windowsfilter" failed to remove root filesystem:
hcsshim::GetComputerSystems: The requested compute system operation is not valid in the current state.
Encountered errors while bringing up the project.

Resolving The Problem

Before we go further, back up Planning Analytics Workspace databases by running these commands in Powershell:
cd <PAWorkspacePath>
./scripts/backup.ps1
Some errors might occur while containers are being stopped or restarted (at the beginning and at the end of the backup script), nevertheless the backup itself is probably valid. So, verify that the databases were correctly backed up, by checking the files in this folder:
<PAWorkspacePath>\backup\backup_<date_and_time>
Here is the list of files:
bss.zip
couchdb.zip
mongo.zip
mongo_db.zip
mysql.zip
redis.zip
Now that a backup is done, we can go on.
Step 1: Re-create containers.
Open Powershell as an administrator (right-click, "Run as administrator") and run these commands:
cd <PAWorkspacePath>
./scripts/paw.ps1 stop
docker rm $(docker ps -a -q)
stop-service docker
start-service docker
./scripts/paw.ps1    (with no command-line options)
Wait about 2 - 3 minutes and run this command to show container states:
./scripts/paw.ps1 ps
For Workspace to work, all containers must be "Up" except "bss-init" and "couchdb-init" that must be in "Exit" state.
Step 2: If the previous step did not work, then delete container files manually.
Open Powershell as an administrator (right-click, "Run as administrator") and run this command:
stop-service docker
Open Windows Explorer and check whether "daemon.json" file exists in "C:\ProgramData\docker\config" folder
If yes, then open this file and check the value of "data-root" parameter if it is defined.
--> If there is no "data-root" parameter or no "daemon.json" file, then delete all files and all subfolders from "C:\ProgramData\docker\containers\" directory.
--> If there is a "data-root" parameter, then delete all files and all subfolders from "<data-root>\docker\containers\"
--> If you receive errors because some files are locked, then:
       -Change the startup type of "docker" service from "Automatic (Delayed start)" to "Manual"
       -Reboot the machine
       -Retry to delete the content of the \containers directory
       -Change the startup type of "docker" service back to "Automatic (Delayed start)"
Now get back to the Powershell window and run these commands:
start-service docker
./scripts/paw.ps1    (with no options)
Wait about 2 - 3 minutes and run this command to show containers state:
./scripts/paw.ps1 ps
For Workspace to work, all containers should be "Up" except "bss-init" and "couchdb-init" that should be in "Exit" state.
Step 3: if it is still not working
If there is an antivirus, then exclude these folders (and subfolders) and applications from being scanned:
  Folders:
          <your-PAW-Path>
    C:\ProgramData\Microsoft\Windows\HNS
    C:\ProgramData\docker
    <your-data-root>\docker
    C:\Program Files\Docker
  Applications, executables:
          C:\Program Files\Docker\docker.exe
    C:\Program Files\Docker\dockerd.exe
    C:\Program Files\Docker\docker-compose.exe
Also, change the "Data Execution Prevention" settings. From Windows Start menu go to the Control Panel:
  - Click System and Security
  - Click System
  - Click Advanced system settings
  - A dialog shows up: click the Advanced tab
  - In Performance section, click "Settings..."
  - Another dialog shows up: click the "Data Execution Prevention" tab
  - Select "Turn on DEP for essential Windows programs and services only"
Step 4: if all the previous steps failed
There is some environmental issue or some third-party tool that prevents Docker from working properly.
As a test, stop as many third-party applications and services as possible, and go through Step 1 again.
If nothing helps, then follow this document and provide the audit log to IBM Support:

Document Location

Worldwide

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCTEW","label":"IBM Planning Analytics Local"},"ARM Category":[{"code":"a8m50000000KzIzAAK","label":"Planning Analytics Workspace"},{"code":"a8m50000000KzKqAAK","label":"Planning Analytics Workspace-\u003EDocker"},{"code":"a8m0z000000blfjAAA","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Version(s)"},{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCTEW","label":"IBM Planning Analytics Local"},"ARM Category":[{"code":"a8m50000000KzIzAAK","label":"Planning Analytics-\u003EPlanning Analytics Workspace"}],"Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]

Document Information

Modified date:
12 April 2023

UID

ibm16407826

Page Feedback