summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFred <f.fredhenry@gmail.com>2024-10-19 12:52:32 -0500
committerFred <f.fredhenry@gmail.com>2024-10-19 12:52:32 -0500
commitbe4c88ddeca0f21e1e7b3ee286a3695ab168cee1 (patch)
tree77ddacd791a6ceb021c21a122d1a5784bf1701fc
parent3e383e46e8da28beee5b107378320e4519a610a3 (diff)
merged commands into readmemain
-rw-r--r--README.md14
-rw-r--r--commands.info6
2 files changed, 14 insertions, 6 deletions
diff --git a/README.md b/README.md
index 8f873d8..15cf7d5 100644
--- a/README.md
+++ b/README.md
@@ -1 +1,15 @@
# volatility2docker
+
+This is the original Volatility memory forensics tool, now as a Docker container.
+While Volatility 3 exists, it doesn't quite have the same mature feature set as
+the original. This can be ran without having to worry about compability issues
+between Python 3 and Python 2.
+
+##### to build the container from the same directory as the Dockerfile
+```
+docker build -t volatility2mint .
+```
+##### to run the container from a host directory with memory images present
+```
+docker run -it --mount type=bind,source=.,target=/userspace volatility2mint
+```
diff --git a/commands.info b/commands.info
deleted file mode 100644
index f0a818f..0000000
--- a/commands.info
+++ /dev/null
@@ -1,6 +0,0 @@
-# to build the container from the same directory as the Dockerfile
-docker build -t volatility2mint .
-
-# to run the container from a host directory with memory images present
-docker run -it --mount type=bind,source=.,target=/userspace volatility2mint
-