Docker Desktop is a powerful tool that allows developers to build, ship, and run applications in containers. By default, Docker stores its images and containers in the system drive, which can sometimes lead to storage space issues. In this blog post, we’ll explore how to change the Docker image installation directory on the Windows platform.
Tested System:
- Lenovo ThinkPad X1
- Microsoft Windows 11 Pro
- 32 GB RAM
- 13th Gen Intel Core i7-1355U
Pre-requisite:
- Install Visual Studio Code
- Install Docker Desktop for Windows
- Ensure that you have installed the latest version of Docker Desktop for Windows 4.26.1.
2. Ensure that “Use the WSL2 based engine” is enabled under Dashboard > Settings > General.
3. Open Settings > Resources > WSL Integration option.
As shown, the current default Docker Image location is C:\Users\ajeet\AppData\Local\Docker\wsl.
Changing the Installation Directory
Go ahead and try changing the default Disk Image location.
Quick Note: The Resource section also allows you to configure limits on the memory, CPU and Swap size allocated to WSL2 by editing the .wslconfig file.
The wsl.conf and .wslconfig files are used to configure advanced settings options, on a per-distribution basis (wsl.conf) and globally across all WSL 2 distributions (.wslconfig). This guide will cover each of the settings options, when to use each file type, where to store the file, sample settings files and tips.
What is the difference between wsl.conf and .wslconfig?
You can configure the settings for your installed Linux distributions that will automatically be applied every time you launch WSL in two ways, by using:
- .wslconfig to configure global settings across all installed distributions running on WSL 2.
- wsl.conf to configure local settings per-distribution for each Linux distribution running on WSL 1 or WSL 2.
Both file types are used for configuring WSL settings, but the location where the file is stored, the scope of the configuration, the type of options that can be configured, and the version of WSL running your distribution all impact which file type to choose.
WSL 1 and WSL 2 run with different architecture and will impact the configuration settings. WSL 2 runs as a lightweight virtual machine (VM), so uses virtualization settings that allow you to control the amount of memory or processors used (which may be familiar if you use Hyper-V or VirtualBox). Check which version of WSL you are running.
Configuring which WSL 2 distros you want to access Docker from
You can “Enable integration with my default WSL distro” under Resources > WSL Integration option.
Conclusion
Changing the Docker image installation directory on Windows is a straightforward process. By selecting a different location with more available space, you can avoid running into storage issues when working with containers.
Remember to be cautious when modifying Docker settings, and always ensure that you have adequate disk space on the chosen drive. Happy containerizing!
Keep Reading
-
Testcontainers and Playwright
Discover how Testcontainers-Playwright simplifies browser automation and testing without local Playwright installations. Learn about its features, limitations, compatibility, and usage with code examples.
-
Getting Started with the Low-Cost RPLIDAR Using NVIDIA Jetson Nano
Conclusion Getting started with low-code RPlidar with Jetson Nano is an exciting journey that can open up a wide range of possibilities for building robotics projects. In this blog post, we covered the basic steps to get started with low-code RPlidar with Jetson Nano, including setting up ROS, installing the RPlidar driver and viewing RPlidar…
-
Docker and Wasm Containers – Better Together
Learn how Docker Desktop and CLI both manages Linux containers and Wasm containers side by side.
-
Deploying NVIDIA NIM for Generative AI Applications
NVIDIA’s NIM (Neural Inference Microservices) provides developers an efficient way to deploy optimized AI models from various sources, including community partners and NVIDIA itself. As part of the NVIDIA AI Enterprise suite, NIM offers a streamlined path to quickly iterate on and build innovative generative AI solutions. With NIM, you can easily deploy a microservice…
-
Integration of Model Context Protocol and Docker AI Agent under Docker Desktop
I recently had the opportunity to collaborate with Raveendiran RR, a Docker Community Speaker and Generative AI enthusiast, to present on this exciting topic at Cloud-Native LLMOps Day in Bengaluru. Together, we explored the transformative potential of Model Context Protocol in modern AI development workflows, sharing insights with the vibrant tech community. This blog post expands on the key…
-
Deploy DeepSeek-R1 using Ollama-Operator on Kubernetes
In this demo, we will walk through the steps to deploy the DeepSeek-R1 quantitative model on your machine using the Ollama Operator for Kubernetes. This operator makes it easy to run large language models on your cluster. The demo below includes installing the operator, deploying a model, and accessing it. Prerequisites A running Kubernetes cluster…
