Uninstallation

Windows

Uninstalling Specific Node Instances

To remove a specific Node instance:

1 Start the inmationSetup.exe with Administrator privileges.

2 In the Modify section, click Service Configuration to open the Service Setup page.

3 In the left-hand panel, select the instance that you wish to remove.

4 Click Remove. A dialog pops up, asking for confirmation. Click OK to confirm the removal of this Node instance. The confirmation dialog is closed and the entry for this Node instance is removed from the instances list.

5 Click OK for the Service Setup page to apply your changes.

If you select Cancel or close the Setup window, the instance will not be removed but listed again when you run the Setup the next time.

6 Another dialog pops up, asking if application files shall be removed.

Only if Yes is selected, the installation folder and the data folder for this instance ( i.e. C:\Program Files\AspenTech\inmation.root.<INSTANCE>\ and C:\ProgramData\AspenTech\inmation.root.<INSTANCE>\ ) are removed together with the service. Selecting No uninstalls the service but keeps these folders in place.

7 The service for the instance (and optionally the related folders, depending on the selection in the previous dialog) is removed, while a progress bar is shown.

8 Once the Node instance is uninstalled, the setup can be closed.

Uninstalling All Node Instances

To uninstall all Node instances:

1 Start the inmationSetup.exe with Administrator privileges.

2 In the Uninstall section, select the checkbox for Remove all instances (default/named) and click Uninstall.

If this checkbox is not selected, only the C:\Program Files\AspenTech\inmation.install folder is removed. The services remain installed and their installation and data folders are left in place.

3 A dialog pops up, asking if application files shall be removed.

  • If Yes is selected, the installation folders and the data folders ( i.e. C:\Program Files\AspenTech\inmation.root.(default/<INSTANCE>)\ and C:\ProgramData\AspenTech\inmation.root.(default/<INSTANCE>)\ ) are removed together with the Node services.

  • Selecting No uninstalls the Node services but keeps the installation folders and data folders in place.

4 While the uninstallation of the services and the removal of the folders takes place, a progress bar is displayed.

5 Once the uninstallation is finished, the setup can be closed.

Linux Containers

Before data can be deleted or container images can be removed, the container to which it belongs needs to be stopped.

Removing Node Containers

This section addresses the following options for removing Node containers:

Before a container can be removed, it needs to be stopped first.

Removing Specific Containers

1 To list all running containers run:

$ docker container ls

To also include containers that currently are not running in the results, append the '-a' argument.

2 To stop one or more specific container(s) run

$ docker stop <CONTAINER_ID_or_NAME> [<CONTAINER_ID_or_NAME>]

3 To remove the container(s) run:

$ docker rm <CONTAINER_ID_or_NAME> [<CONTAINER_ID_or_NAME>]

Removing All Containers

1 To stop all containers run:

$ docker stop $(docker container ls -q)

With the '-q' argument, the inner command returns a only IDs all running containers.

2 To remove all containers run:

$ docker rm $(docker container ls -a -q)

Removing All Containers of a Docker Compose File

To stop and remove all containers of a docker compose file run:

$ docker compose -f 'docker-compose.yml' down
Optionally removing data

If you are absolutely sure about it, the data for this container can be deleted (i.e. the volume removed) by adding the '- v' argument to the command as in shown here:

$ docker compose -f 'docker-compose.yml' down -v

Removing Node Data

The Node data is stored in Docker volumes that are mounted for the specific containers. When the volume is removed, the Node data is deleted.

This section addresses following options for removing volumes:

Removing Specific Volumes

To be able to remove the volume, the container to which the volume belongs needs to be stopped first, and then removed.

1 Make sure that the container to which the volume belongs is already removed, follow these steps:

1 List all volumes to identify the one you want to remove:

$ docker volume ls

2 Identify the container to which the volume belongs:

$ docker container ls -a --filter volume=<VOLUME_NAME>

3 Stop the container:

$ docker container stop <CONTAINER_ID_or_NAME>

4 Remove the container:

$ docker container remove <CONTAINER_ID_or_NAME>

2 Once the container is removed, the volume can be removed:

$ docker volume rm <volume_name> [<volume_name>]

Removing all Volumes of A Compose File

If you are absolutely sure that you want to remove the data for all Nodes defined in the compose file, this can be done by by adding the '- v' argument when stopping and removing all containers of a compose file as shown here:

$ docker compose -f 'docker-compose.yml' down -v

Removing Docker Images

When a docker image is no longer used by any container, it can be removed.

1 To list existing images run:

$ docker image ls

2 To remove one or more specific images run:

$ docker image rm <IMAGE_ID>