Docker Desktop uses a private IPv4 network for internal services such as a DNS server and an HTTP proxy. In case Docker Desktop's choice of subnet clashes with IPs in your environment, you can specify a custom subnet using the **Network** setting.
On Windows and Mac, you can also set the default networking mode and DNS resolution behavior. For more information, see [Networking](/manuals/desktop/features/networking.md#networking-mode-and-dns-behaviour-for-mac-and-windows).
On Mac, you can also select the **Use kernel networking for UDP** setting. This lets you use a more efficient kernel networking path for UDP. This may not be compatible with your VPN software.
### WSL Integration
On Windows in WSL 2 mode, you can configure which WSL 2 distributions will have the Docker
WSL integration.
By default, the integration is enabled on your default WSL distribution.
To change your default WSL distribution, run `wsl --set-default <distribution name>`. (For example,
to set Ubuntu as your default WSL distribution, run `wsl --set-default ubuntu`).
You can also select any additional distributions you would like to enable the WSL 2 integration on.
For more details on configuring Docker Desktop to use WSL 2, see
[Docker Desktop WSL 2 backend](/manuals/desktop/features/wsl/_index.md).
## Docker Engine
The **Docker Engine** tab allows you to configure the Docker daemon used to run containers with Docker Desktop.
You configure the daemon using a JSON configuration file. Here's what the file might look like:
```json
{
"builder": {
"gc": {
"defaultKeepStorage": "20GB",
"enabled": true
}
},
"experimental": false
}
```
You can find this file at `$HOME/.docker/daemon.json`. To change the configuration, either
edit the JSON configuration directly from the dashboard in Docker Desktop, or open and
edit the file using your favorite text editor.
To see the full list of possible configuration options, see the
[dockerd command reference](/reference/cli/dockerd/).
Select **Apply & Restart** to save your settings and restart Docker Desktop.
## Builders
If you have turned on the
[Docker Desktop Builds view](/manuals/desktop/use-desktop/builds.md), you can use the
**Builders** tab to inspect and manage builders in the Docker Desktop settings.
### Inspect
To inspect builders, find the builder that you want to inspect and select the
expand icon. You can only inspect active builders.
Inspecting an active builder shows:
- BuildKit version
- Status
- Driver type
- Supported capabilities and platforms
- Disk usage
- Endpoint address
### Select a different builder
The **Selected builder** section displays the selected builder.
To select a different builder:
1. Find the builder that you want to use under **Available builders**
2. Open the drop-down menu next to the builder's name.
3. Select **Use** to switch to this builder.
Your build commands now use the selected builder by default.
### Create a builder
To create a builder, use the Docker CLI. See
[Create a new builder](/build/builders/manage/#create-a-new-builder)
### Remove a builder
You can remove a builder if:
- The builder isn't your [selected builder](/build/builders/#selected-builder)
- The builder isn't [associated with a Docker context](/build/builders/#default-builder).
To remove builders associated with a Docker context, remove the context using
the `docker context rm` command.
To remove a builder:
1. Find the builder that you want to remove under **Available builders**
2. Open the drop-down menu.
3. Select **Remove** to remove this builder.
If the builder uses the `docker-container` or `kubernetes` driver,
the build cache is also removed, along with the builder.
### Stop and start a builder
Builders that use the
[`docker-container` driver](/build/builders/drivers/docker-container/)
run the BuildKit daemon in a container.
You can start and stop the BuildKit container using the drop-down menu.
Running a build automatically starts the container if it's stopped.