Small improvements in the local dev containers docs (#23702)

---------

Co-authored-by: emily-shen <[email protected]>
Co-authored-by: Jun Lee <[email protected]>

Author: 3 people

src/content/docs/workers/wrangler/configuration.mdx

@@ -1222,6 +1222,14 @@ You can configure various aspects of local development, such as the local protoc
 
   - Host to forward requests to, defaults to the host of the first `route` of the Worker.
 
+- `enable_containers` <Type text="boolean" /> <MetaInfo text="optional" />
+
+  - Determines whether to enable containers during a local dev session, if they have been configured. Defaults to `true`. If set to `false`, you can develop the rest of your application without requiring Docker or other container tool, as long as you do not invoke any code that interacts with containers. 
+
+- `container_engine` <Type text="string" /> <MetaInfo text="optional" />
+
+  - Defaults to `unix:///var/run/docker.sock`. Set this to the socket path your container engine is listening at if you are using another container tool besides Docker, such as `colima`, or if your Docker engine is configured to listen at a path other than `unix:///var/run/docker.sock`. You can also set this via the environment variable `WRANGLER_DOCKER_HOST`.
+
 Example:
 
 <WranglerConfig>

src/content/docs/workers/wrangler/system-environment-variables.mdx

@@ -67,7 +67,10 @@ Wrangler supports the following environment variables:
 
   * By setting this to `0`, you can disable Wrangler's colorised output, which makes it easier to read with some terminal setups. For example, `FORCE_COLOR=0`.
 
+* `WRANGLER_DOCKER_HOST` <Type text="string" /> <MetaInfo text="optional" />
 
+  * Defaults to `unix:///var/run/docker.sock`. Set this to the socket path your container engine is listening at if you are using another container tool besides Docker, such as `colima`, or if your Docker engine is configured to listen at a path other than `unix:///var/run/docker.sock`.
+    You can also set this via `container_engine` config option.
 
 
 

src/content/partials/workers/bindings_per_env.mdx

@@ -16,6 +16,7 @@ You can configure [**remote bindings** during local development](/workers/develo
 | **Browser Rendering**                   |        ✅         |             ✅             |
 | **D1**                                  |        ✅         |             ✅             |
 | **Durable Objects**                     |        ✅         |             ❌             |
+| **Containers**                          |        ✅         |             ❌             |
 | **Email Bindings**                      |        ✅         |             ✅             |
 | **Hyperdrive**                          |        ✅         |             ❌             |
 | **Images**                              |        ✅         |             ✅             |
@@ -46,6 +47,7 @@ Supported only in [`wrangler dev --remote`](/workers/wrangler/commands/#dev) - t
 | **Browser Rendering**                   |         ✅         |
 | **D1**                                  |         ✅         |
 | **Durable Objects**                     |         ✅         |
+| **Containers**                          |         ❌         |
 | **Email Bindings**                      |         ✅         |
 | **Hyperdrive**                          |         ✅         |
 | **Images**                              |         ✅         |
@@ -57,5 +59,3 @@ Supported only in [`wrangler dev --remote`](/workers/wrangler/commands/#dev) - t
 | **Service Bindings (multiple Workers)** |         ✅         |
 | **Vectorize**                           |         ✅         |
 | **Workflows**                           |         ❌         |
-
----