docs: update FAQ

Signed-off-by: Abiola Ibrahim <[email protected]>

docs/FAQ.md

@@ -44,6 +44,7 @@
     - [Docker Compose and Buildx showing runc error](#docker-compose-and-buildx-showing-runc-error)
       - [Version v0.5.6 or lower](#version-v056-or-lower)
     - [Issue with Docker bind mount showing empty](#issue-with-docker-bind-mount-showing-empty)
+  - [How can Docker version be updated?](#how-can-docker-version-be-updated)
 
 ## How does Colima compare to Lima?
 
@@ -405,3 +406,9 @@ From v0.5.6, start Colima with `--cgroups-v2` flag as a workaround.
 When using docker to bind mount a volume (e.g. using `-v` or `--mount`) from the host where the volume is not contained within `/tmp/colima` or `/Users/$USER`, the container will start without raising any errors but the mapped mountpoint on the container will be empty.
 
 This is rectified by mounting the volume on the VM, and only then can docker map the volume or any subdirectory. Edit `$COLIMA_HOME/default/colima.yaml` and add to the `mounts` section (examples are provided within the yaml file), and then run `colima restart`. Start the container again with the desired bind mount and it should show up correctly.
+
+## How can Docker version be updated?
+
+Each Colima release includes the latest Docker version at the time of release.
+
+From v0.7.6, there is a new `colima update` command to update the container runtime without needing to update Colima or to wait for the next Colima release.