Remove Docker files from repository

INSTALL.md

@@ -58,11 +58,6 @@ configuration options.
 
 ## Known Issues / To-do's:
 
-- The newest LLVM version supported is 3.6.2. We ran out of time during 0.104
-  development to add support for newer versions of LLVM.
-  The bytecode interpreter is therefore the default option for the bytecode
-  signature runtime in this release.
-
 - Complete the `MAINTAINER_MODE` option to generate jsparse files with GPerf.
 
 - The test suite will fail to run if you have `pytest` from Python2 installed
@@ -93,7 +88,6 @@ For Maintainer-mode only (not recommended):
 - Flex
 - Bison
 - Gperf
-- Rust bindgen
 
 ### External Library Dependencies
 
@@ -159,7 +153,7 @@ mkdir build && cd build
 
 ## CMake Basics
 
-CMake isn't actually a built system. It's a meta-build system. In other words,
+CMake isn't actually a build system. It is a meta-build system. In other words,
 CMake is a build system *generator*.
 
 On Unix systems, CMake generates Makefiles by default, just like Autotools.

NEWS.md

@@ -95,6 +95,13 @@ ClamAV 1.0.0 includes the following improvements and changes.
   compatibility issues. Patch courtesy of Matt Jolly.
   - GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/692
 
+- Moved the ClamAV Docker files for building containers to a new Git repository.
+  The Docker files are now in https://github.com/Cisco-Talos/clamav-docker.
+  This change enables us to fix issues with the images and with the supporting
+  scripts used to publish and update the images without committing changes
+  directly to files in the ClamAV release branches.
+  - GitHub pull request: https://github.com/Cisco-Talos/clamav/pull/764
+
 ### Bug fixes
 
 - Assorted code quality fixes. These are not security issues and will not be

README.Docker.md

@@ -35,7 +35,19 @@ You can use the `unstable` version (i.e. `clamav/clamav:unstable` or
 
 While it is recommended to pull the image from our
 [Docker Hub registry](https://hub.docker.com/u/clamav/clamav), some may want
-to build the image locally instead. All that is needed is:
+to build the image locally instead.
+
+To do this, you will need to get the  `Dockerfile` and the supporting `scripts/`
+directory from the
+[clamav-docker Git repository](https://github.com/Cisco-Talos/clamav-docker).
+Be sure to select the correct one for this ClamAV release.
+
+> _Tip_: For unreleased ClamAV versions, such as when building from the `main`
+> git branch, you should select the files from the
+> `clamav-docker/clamav/unstable/<distro>` directory.
+
+Place the `Dockerfile` and `scripts/` directory in the ClamAV source directory.
+Then you can build the image. For example, run:
 ```bash
 docker build --tag "clamav:TICKET-123" .
 ```