Skip to content

README_preprocessor.md

Latest commit

 

History

History
539 lines (338 loc) · 34.7 KB

README_preprocessor.md

File metadata and controls

539 lines (338 loc) · 34.7 KB

FINN Preprocessor

The first step to create FINNv2 emission estimates is to produce the FINN input file. This file is a comma-delimited text file that includes the fire locations, burned area, and underlying information about the land cover and vegetation burned. This preprocessor creates the FINN input file for a given set of fire detections (MODIS and/or VIIRS). Specifically, this is a PostGIS-based preprocessor. Given a point feature shapefile of active fire detections, this code estimates burned region, and then determines land cover on the burned area. The output from this code is a *.csv file that will be used to estimate emissions with the FINN emissions processor.

Instructions

Note - Paragraphs starting with an icon ℹ️ can be skipped. They are FYI only.

Note - the instructions here are for all supperted operating systems (Windows, Mac, and Linux). However, there are specific notes throughout for Windows users (Docker Desktop for Windows). There are extra information specific to different operations system, version of Docker product (Desktop vs. Toolbox), and please refer to them as needed.

The user is expected to provide the MODIS and/or VIIRS fire detection shapefile for the time and spatial extent to be processed. The user can request these files from the NASA Fire Information for Resource Management System (FIRMS). Information about the VIIRS and MODIS products are at:
https://earthdata.nasa.gov/earth-observation-data/near-real-time/firms

To request archived data, the user can go to the Archive Download: https://firms.modaps.eosdis.nasa.gov/download/

Users can also request the active fire data for up to 7 days ago at:
https://earthdata.nasa.gov/earth-observation-data/near-real-time/firms/active-fire-data

Users can chose MODIS and/or VIIRS fire detections. When requesting data, the shapefile file format should be chosen.

1. Prerequiste

Before running this code, the user must have accounts set up and software installed. Specifically,

1.1 EarthData Login

The user must have an EarthData login (this is necessary for downloading the required MODIS LCT and VCF products). If you do not have a NASA EarthData account, you can create one here:
https://urs.earthdata.nasa.gov/
The account is used in order to download land cover raster dataset from EarthData.

1.2 Download required software to your computer

The following software must be downloaded and installed on your computer:

For those using Windows:
Powershell is recommended as your command line terminal. To open the PowerShell, type PowerShell in the Windows search bar. This program will open a terminal in which you can use command lines to run the programs (see screeen shots in wiki page).

Linux/Mac user can use the OS's default terminal.

2. (Windows/Mac) Customize virtual machine

Windows/Mac requires customization of Docker environment.

Specific instuction for Docker Desktop can be found in the wiki page at 3 Customize Docker Setting of the Project Wiki page for Docker-Desktop.

Specific instruction for Docker Toolbox can be found in the wiki page at 2 Configure Oracle VM Virtual Machine

** For Docker Toolbox, make sure you do this before going further (after you install Docker to your computer).** Docker Desktop's configuration can be changed later as needed.

3. Acquiring this repository

Note for Windows Users: Open a PowerShell terminal and navigate to the directory on your computer where you want to store and run command in sections 3, 4 and 5 of this README file.

To get this repository locally, use git clone:

git clone https://github.com/NCAR/finn.git
cd finn/preprocessor

Alternatively Download ZIP button is available at https://github.com/NCAR/finn (or direct link https://github.com/NCAR/finn/archive/master.zip )

Next, copy your fire detection shapefile(s) into the directory ../finn/preprocessor/data/. These files need to be UNZIPPED.

The "All_countries" shape file (used for assigning global region) can be retrieved from: https://ftp.acom.ucar.edu/user/emmons/FINN_region_shapefiles/

4. Building the Docker image

The next step is to build the Docker image. To build the Docker image, execute the following command from the terminal, in the directory where Dockerfile exists (this project directory):

docker build -t finn .

Look for an output line that says "Successfully built ..." and "Successfully tagged finn:latest". The security warning that may follow can be ignored.

To verify that the image is created, type docker image ls. One record should list finn as a REPOSITORY (specified by -t finn option).

5. Manage the Docker container

The next step is to create your Docker container and then run the code within it. This is still done within the terminal (for Windows users, continue in PowerShell).

5.1 Create and start

Create and start the container via docker run, mounting the current working directory to the location /home/finn in the container.

Note: In the commands below, replace yourusername and yourpassword with your NASA EarthData username and password (note that if you have special characters in your username or password, you may need to escape those characters or use quotes, e.g., password\! or 'password!'). REMEMBER: If you do not have a NASA EarthData account, you can create one here: https://urs.earthdata.nasa.gov/ You should only have to do this once.

(Linux)

# Create directory in your home directory to store the database
mkdir ${HOME}/pg_data

docker run --name finn -v $(pwd):/home/finn -v ${HOME}/pg_data:/var/lib/postgresql -p 127.0.0.1:5432:5432 -p 8888:8888 -d -e EARTHDATAUSER=yourusername -e EARTHDATAPW=yourpassword finn

(Mac) Same command for Linux may work but using volume mount may be more stable.

# Create named volume to store the database
docker volume create pg_data

docker run --name finn -v $(pwd):/home/finn -v pg_data:/var/lib/postgresql -p 127.0.0.1:5432:5432 -p 8888:8888 -d -e EARTHDATAUSER=yourusername -e EARTHDATAPW=yourpassword finn

(Windows Powershell for Docker Desktop, the latest Docker on Windows)

# Create named volume to store the database
docker volume create pg_data

# Function to convert windows path to what docker likes
filter docker-path {'/' + $_ -replace '\\', '/' -replace ':', ''}

# Create docker container and start
docker run --name finn -v ( (pwd | docker-path) + ':/home/finn') -v pg_data:/var/lib/postgresql -p 127.0.0.1:5432:5432 -p 8888:8888 -d -e EARTHDATAUSER=yourusername -e EARTHDATAPW=yourpassword finn

(Windows Powershell for Docker Toolbox, the legacy Docker on Windows)

# Create named volume to store the database
docker volume create pg_data

# Function to convert windows path to what docker likes
filter docker-path { '/' + $_.tostring().substring(0,1).tolower() + $_.tostring().substring(1) -replace '\\', '/' -replace ':', ''}

# Create docker container and start
docker run --name finn -v ( (pwd | docker-path) + ':/home/finn') -v pg_data:/var/lib/postgresql -p 127.0.0.1:5432:5432 -p 8888:8888 -d -e EARTHDATAUSER=yourusername -e EARTHDATAPW=yourpassword finn

To verify that the container is running, type docker ps. You should see the container listed with a unique container id, the name "finn" and some other information.

NOTE: If you get an error saying that container name "finn" already in use, then you need to either (1) get rid of it first and docker run again, or (2) use different name for --name finn part, e.g. --name finn_second, in the command above.

If you did approach (2), you start having multiple containers for finn, so make sure you keep track of which is what. Container finn is already there, and you now has container finn_second.

If you rather take approach (1), type:

docker stop finn
docker container rm finn

These should remove the pre-existing container finn and you should be able to docker run now.

If this still doesn't work, you may want to try retarting Docker. If you are using Docker Desktop for Windows,

  • Go to Docker whale symbol, right click, and select restart
  • Once it's started again, go back to the PowerShell and type docker start finn. Instead of docker run after restarting docker, You would try docker start finn. This is because docker run creates containers and starts it. If it fails, it may be that container is created but failed to started. After restarting docker, the container you have already created may work by just starting it, docker start finn

ℹ️ Below the meaning of each options for docker run.

  • --name finn This sets the name for the container. Happened to be the same as image's name, but you may choose other names (to have multiple containers out of one image). You cannot use same name for two different containers, though, container name must be unique.
  • -v $(pwd):/home/finn
    This makes $(pwd) (current working directory, where you downloaded FINN preprocessor by Git) to be accessible as /home/finn from inside the container being made ( bind mounts ). Therefore the change you make in FINN directory on your machine is reflected immediately in files in /home/finn in the container and vice versa, since they are identical file on the storage. Our code/inputs/intermediate files/outputs is stored in FINN direoctory which becomes /home/finn when you look from the container.
  • (Linux/Mac) -v ${HOME}/pg_data:/var/lib/postgresql
    Does bind mounting again, mounting pg_data directory you created (this can be anywhere on your machine) to the container's /var/lib/postgresql directory. The directory is used by PostgreSQL/PostGIS running in container to store the database. With this setting, database itself becomes independent of the container. Instead of ${HOME}/pg_data you can use any directory in your system.
  • (Windows) -v pg_data:/var/lib/posrgresql
    Unfortunately this setting does not work for Windows version of Docker since the host machine's files system is not compatible of PostgreSQL in the container (Linux version). Instead we recommend to create named volumes and store database there. See project wiki page for volume management for more detail.
  • -p 127.0.0.1:5432:5432 and -p 8888:8888 Maps container's port for PostgreSQL and Jupyter Notebook to those on the host machine. You can, for example, -p 25432:5432 if your machine uses 5432 for other purpose. 127.0.0.1 part is to let only the machine with the address, i.e., the host machine running the docker container, to access the port.
  • -d Makes the container be detached from the terminal you created container (makes it a daemon)
  • -e EARTHDATAUSER=yourusename and -e EARTHDATAPW=yourpassword The code has functionality to download MODIS raster data from Earthdata website, and they require you to register to do that. Create one if you plan to use MODIS raster directly downloaded from Earthdata website.
  • finn at the end refers to docker image finn created by docker build command earlier.

5.2 Start Jupyter Notebook from the container

Once the container is running, you can launch a jupyter notebook using docker exec:

docker exec -it finn jupyter notebook --ip=0.0.0.0 --port=8888 --allow-root --notebook-dir /home/finn

You should see something like the following in your terminal:

    To access the notebook, open this file in a browser:
        file:///root/.local/share/jupyter/runtime/nbserver-814-open.html
    Or copy and paste one of these URLs:
        http://2daf0642bf75:8888/?token=9024c305edb954921c35832f3f7f47388326a14a804eb8cd
     or http://127.0.0.1:8888/?token=9024c305edb954921c35832f3f7f47388326a14a804eb8cd

The Jupyter notebook (and the code there) will be run from a web browser.

Open a web brower, and in address bar, copy/paste the URL in the last line. In the above example it would be

http://127.0.0.1:8888/?token=9024c305edb954921c35832f3f7f47388326a14a804eb8cd

This will take you to the Jupyter notebook.

Note that your token (the part after token=...) will be different.

If running on a remote server (e.g., an Amazon EC2 instance) replace localhost with the server's IP address.

6. Running the notebook

From this point forward, leave the terminal open and move to the newly opened web browser.

To open the notebook, navigate to the work_generic/ directory and open main_generic.ipynb by double clicking on that file. The code on this page runs the FINN preprocessor, including the components related to downloading MODIS land cover and vegetation data. The user is able to run a test case or to run a specific time and location for which the user has already downloaded fire detections.

6.1 Run the test case

It is highly recommended at this point to run 'main_generic.ipynb' as it is, to verify that your local copy is working as expected. If run is successful, your output should look something similar to 'main_generic.html' which is hard copy version of ipynb with results.

There are a few ways to run code. You can press the Run button at the top, which will run one cell at a time. (so you have to click it through the entire page), or you can go to Cell -> Run All from the top bar.

Next to each cell is In [ ]:. When there is a In [*]:, the cell is cued up to run. When there is a number in there, the results are finished.

At the end of the run, your FINN input file will be in the directory of the name that you chose in the first cell. For the test case it will be "out_testOTS_092018_modlct_2017_modvcf_2017_regnum.csv". The created file will be a comma-delimited file that can be used as input to the FINN emissions code.

6.2 Run your case

Once you run the test case successfully you are ready to run your case.

It is recommened to create copy of work_generic directory, keeping only main_generic.ipynb, and do your work in separate directory. In that way you can keep work related to one processing of active fire datasets in one place, not mixing with other results.

Before running, user first edit the first cell (the coded part that is shaded in gray) in "Section 1". Instructions in Section 1 include information about what to edit. Read this and then edit the first cell. Make sure you have the correct path to the input fire detection shapefile(s) and the year.

There are three more cells in Section 1, although you can keep them as is. They are for what raster dataset to use (not really supported well at this point, December 2019), creating extra ouput (all True by default) and deleting intermediate files (all False by default)

Once you have edited the first cell, you can go ahead and run the code, as you did for test case.

NOTE: If running a recent year, the year-specific MODIS LCT and VCF files may not be yet available. This will lead to an error statement in Section 5. If the year-specific data are unavailable, we recommend choosing the most recent year available for your processing. You will have to go back and edit the first cell and restart the kernel.

NOTE: Minimum instructions to use QGIS available to visualize burned area and raster dataset stored in PostGIS.

7 What you'd do day-to-day

You may want to shut down, leave the computer, come back next day to continue you rowrk. Use the comamnd below.

Stopping the container

When you are done for the day, you should stop container. To do this, follow these instructions:

First stop the Jupyter Notebook application by typing ctrl+C in the terminal that started the Notebook. Then use following command.

docker stop finn

finn here refers to the name of container, the --name option you used in docker run. docker ps shows all running containers (or docker container ls). Use docker ps -a to see all container including ones that is stopped.

Start again

To start the container again and continue your work, e.g. later days, use following command.

docker start finn

This command take you to the place right after docker run, as in section 5.1 above, except that creating new container, you are reusing the existing container. Generally no need to redo the "docker run". Instead use "docker start" to reuse existing container.

Once container is started, you can open the notebook using command in section 5.2

docker exec -it finn .....
List running containers

If you're not sure whether there are any Docker containers currently running, you can check with:

docker ps

If nothing is running, then all you will see is a header:

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS

Otherwise, there will be information below these headers about the container(s) that is running.

ℹ️ Diagram below shows components of docker involved in FINN preprocessor. You would notice where this docker run, exec, start and stop fits in. Please refer to descriptoins in Section 9.4 below for more.

docker components

8 Database Backup/Restore

If for some reason you want to create a backoup copy of PostGIS database (the data used in finn-processors), here is how. Keep in mind that final output are exported as CSV and SHP files. Also, the content of database persists until you deliberately delete them (or unseeable system failure). These are only needed for the capability of review work after the FINN and/or FINN preprocessor is removed, or you need to move the database as is from one machine to another.

Databese backup can be done with pg_dump command.

docker exec finn sudo -u postgres pg_dump finn -f /home/finn/finn.dmp

This created a postgresql dump file (text file with SQL command to restore data) in /home/finn, which is the same as where you downloaded finn from GitHub.

Restoration can be done with psql command with the dump file. Example below creates new container that restores backed up data.

First, create new docker volume (virtual disk space where PostGIS databse is stored).

docker volume create pg_data2

Create new docker container 'finn_testrestore' to restore database (example below is for powershell. user appropriate path for first -v option if you are on different OS).

docker run --name finn_testrestore -v ( (pwd | docker-path) + ':/home/finn') -v pg_data2:/var/lib/postgresql -p 5432:5432 -p 8888:8888 -d -e EARTHDATAUSER=yourusername -e EARTHDATAPW=yourpassword finn

Restore the database from backup finn.dmp that was created earlier.

docker exec finn_testrestore sudo -u postgres psql -d finn -f /home/finn/finn.dmp

Now new container finn_testrestore has it's own PostGIS database (stored in pg_data2 on docker virtual machine). You can, for example, export the output (last part of main_XXX.ipynb to export output without running them.

9. Tidy up by removing intermediate or unneeded data

The preprocessor accumurates intermediate data as files and also data in database. This section describes how to reclaim diskspace used by finn preprocessor.

9.1 Removing intermediates as soon as code runs

This is what i tried by four options near the beginging of script, Section 1., 'wipe_intermediate_vector_in_db', 'wipe_downloaded_hdf', 'wipe_intermediate_geotiff' and 'wipe_intermediate_rst_in_db'. Problem is that it is not straight forward if user want to use this capability some later day (after the notebook shutdown, and later restarted), because variables being used are set in the code embedded in the middle of code, and restoring them is not stratighforward. At this point, you may have to do manual delete as described in Sections 9.2 and 9.3.

9.2 Removing raw MODIS imagery and intermediate raster data

If you need to remove files to free up hard disk space after running the FINN preprocessor, you can do so by running the following commands in a cell at the end of a Jupyter notebook:

!rm -rf ../downloads/
!rm -rf ../proc_rst*

The first command removes the downloads directory which has copy of raw MODIS imagery (hdf files) on EarthLab. Second command removes all directories that starts with proc_rst, where intermediate raster files are created. ALternatively you can use your system's methods (e.g. rm in terminal, Windows Explorer to remove files) to remove the files/directories.

9.3 Removing intermediate fire detection/burned area processing data

The active fire shape file you downloaded from FIRMS website is imported into PostGIS database, and has several intermediate format in the database. The disk use by the database is checked from Jupyter notebook by !du -sh /var/lib/postgresql. With annual, global processing using combined MODIS/VIIRS detection, disk use was 48GB.

Or directly from your computer by one of following ways, depending on your OS.

If you use linux, du -sh $HOME/pg_data . This is where we decided to store database when you created container (docker run).

If you use Windows and using Docker Destkop for Windows, easiest way to check diskuse from Windows is to find the size of C:\Users\Public\Documents\Hyper-V\Virtual hard disks\MobyLinuxVM.vhdx. This is the virtual disk image (disk space) for Linux virtual machine. Docker is started from this Linux virtual machine, and FINN preprocessor is running on top of docker. When finn prorpocessor is set up but starting any analysis, the size of this file was about 10GB. After running global, annual, MODIS/VIIRS combined case, the size grew to 76GB.

In order to wipe intermediate data in the database, you'd have to delete each schema in the database. At this point, suggested approach for manually deleting those intermediate would be to use QGIS to access the postgis database (hostname = localhost, port = 5432, databse = finn, user = finn, password = finn), use DB manager (from manu, Databae => DB Manager...), connect to database (PostGIS, new connection, and specify access information), and identify af_XXX schema where you dont need to keep, and also tables in raster schema for imported raster you dont need. Please refer to the mini-QGIS guide, although it does not cover the part removing data. It should help how to access the tables in the database.

Another possibility is pgAdmin 4 which allows managing databse contents. Lastly you can use psql (command line interface of postgresql).

I try to write a notebook which allows this management/cleanup at some point, if i have enough time. Let me know if you need this feature desperately, i try harder to find time.

9.4 Remove/Recreate/Update docker components

Overview of docker components

ℹ️ Diagram below shows components of docker involved in FINN preprocessor, same diagram as you see in subection 7.

docker components

The day-to-day task covered in this subsection 7 deals with docker container, represented by boxes starting with "Run" and ending with "Conteiner Rm". Blue arrows indicates that container is running, and docker exec can be issued on the container. "Stop"/"Start" cycle can be repeated as many times. You will also note that docker build and docker volume create commands creates "image" and "volume" respectively. These exists independently until you explicitly delete them.

FINN preprocessor is designed to save data that you download/generate to be saved outside of Docker system for better persistence of data. First, all of your downloaded files and intermediate data are stored in finn/preprocessor directory which you created near begining. We are using docker's "bind-mount" method to access the directory both from inside and outside of docker.

Another location where FINN store data is PostgreSQL (PostGIS) database. For Linux/Mac users, this is $HOME/pg_data directory, and is "bind-mount"ed similarly to finn/preprocessor. The data there can be reused (more later). For Windows users, we created "named volume" pg_data by command docker volume create pg_data. This will set a directory inside Linux virtual machine (Hyper-V), and docker container is going to access the space to store the database. Life of docker named volume is independent of docker images and containers, and it persist unless you explicitly delete the volume.

Following section has commands for deleting cocker components used in FINN. With the exception of removing docker volumes, these have little effects on disk use, as FINN preprocer does not store data in containers/images.

Removing the container

To permanently delete the FINN container, you have to first stop the container docker stop finn, then you can use:

docker rm finn

or

docker container rm finn

Note that this does not delete the files in finn_preproc directory, or the PostgreSQL database stored inside docker volume (Windows) or $HOME/pg_data (Linux/Mac). It simply remove the container which can be easily recreated, by docker run command described in Section 5.1. By using argumeents for -v pg_data:/var/lib/postgresql (or -v ${HOME}/pg_data:/var/lib/postgresql for Linux), the content of database is unaffected, and all the data you created earlier are still available as it was before removing the container.

Removing the image

You have to first remove container made from the image, following the instruction above. If you created more than one container from the image, all of containers needs to be removed.

docker rmi finn

or

docker image rm finn

Again, this does not remove any files in finn/preprocessor directory, or the PostgreSQL database. Image can be recreated with docker build command described in Section 4.

Removing the volume

This applies to Windows users, which uses docker volume create to create named volume to house the PostgreSQL database.

docker volume rm pg_data

This will wipe the PostgreSQL datbase (PostGIS database) stored in Linux virtual machine. You can now start from Section 5 to create new volume (docker volume create) and create container (docker run). The database for this new container is near empty.

ℹ️ The content of pg_data is native format for the specific versoin of PostgreSQL. If you copy the entire directory/files to somewhere and let postgreSQL to point to the directory, the database starts with the data. This means that that if you have copy of entier pg_data in somewhere safe, you can start the database by restoring the content. To be specific, you first wipe the pg_data as specified here (or rm -fr ${HOME}/pg_data for linux), and then create new docker volume/container to have fresh databse. You stop the container, and overwrite the content of pg_data with copy of older versoin. You start the docker container, then the database is populated with the old data. This could be an alternative way to backup/restore the database, rather than the canonical method of creating database dump as explained in Secton 8. This is easy for Liunx, as pg_data is a directory in host machine. A log harder to actually do this, because you have to get into Hyper-V linux virtual machine to do the same (this tool lets you do this https://github.com/justincormack/nsenter1). Moreover, you have to make sure that file ownership is set correctly after restoring data: PostgreSQL for Linux is pecific about file ownership, and this was the reason why we have to use named volume (diskspace inside Linux virtual machine), instead of bind-mounte volume (directly accessing host computer's diskspace) for Windows application.

10 Update FINN

Note that updating FINN code won't affect your data on the database you have worked on, or input/output you have generated. It only updates the code to create them. The only exception that you may loose your work in main_generic.ipynb. Update will wipe what you have done to the file. If have customized the file, you save the file with different name before you update FINN. Better yet, you save in different name if you customized the file (e.g., save as work_global_2016/main_global_2016.ipynb for global run for year 2016).

First stop running containers and remove. Remove the image as well.

docker stop finn
docker container rm finn
docker image rm finn

In the Terminal, navigate to main directory ../finn/preprocessor
Then type:

git checkout -- .
git pull

You now recreate image (docker build as in Section 4) and container (docer run as in Section 5.1).

11. Disaster recovery

Try this first, restart the container

Stop container and start again. See section 7 for instructions.

Restart docker

Sometimes, restarting the container does not resolves the glitches introduced at runtime. We noticed several times that restarting docker will resolve the unpredictable behavior of docker container.

For docker desktop for Windows, System taks tray have the whale icon for Docker Desktop. You can right-click the icon and choose Restart.... On linux, you can sudo service docker restart

Check if the system has changed in any way

From our experiences, docker may appear to stop functioning because changes in your system. We observed that

  • If you started VPN, docker may lose access to local storage. As a result you cannot see the conent of FINN preprocessor directory from docker (e.g. Jupyter Notebook). Stop the VPN and restart the container (docker stop finn and then docker start finn)
  • If you changed password for your machine or domain, it may affects docker. On Docker Desktop for Windows, you can go to the setting (right click the system tray icon for docker), go to Shared Drive tab, and Reset credentials. Then enable the shared drive again.
  • You have to be in a user group docker in order to use docker. Make sure that you are in docker user. Instruction for Docker Desktop for Windows are found here. Linux instruction is "Manage Docker as a non-root user" section in thie page.
Recreate container/image/volume

From our experience, this usually does not resolves the "disaster", i.e. Docker suddenly stop working. This is more of tidy up task. Go through three kind of Docker rm commands to remove docker componets (container, image and volume). You can then start again from Section 4.

Last resort, i.e. start over

To wipe everything and start over, you have to reomve (1) everytinng in finn_postproc directory, and (2) remove all docker components (container, image, volume).

For (1), you can do it by Windows Explorer, for example. User appropriate method for your system to remove files/directories.

For (2), one way to do this is remove stop/remove all containers, remove images, remove volumes.

Series of commands below deos that on GNU bash and Windows power shell.

# stop/delete all containers
docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)

# delete all images
docker rmi $(docker images -a -q)

# delete named volumes
docker volume rm $(docker volume ls -q)

After above being completed, you should get only one line each of column header, without actually having any entries. Then the docker environment is clean and you can start over.

# verify no container, expect one line shown below
docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

# verify no image, expect one line shown below
docker images -a

REPOSITORY TAG IMAGE ID CREATED SIZE

# verify no named volume, expect one line shown below
docker volume ls

DRIVER VOLUME NAME

An easier way to remove docker components for Windows is to uninstall the docker desktop. Go to Control Panel ==> Programs and Features and unistall Docker Desktop. The action wipes out the Linux virtual machine (Hyper-V virtual machine) created for Docker, and in effect wipe everything out. You can then start from Section 1.
⚡