Where Are Docker Volumes Located When Running Wsl Using Docker Desktop
“When running Windows Subsystem for Linux (WSL) using Docker Desktop, the Docker volumes are typically located in a specific directory within its Linux file system, providing an advantageous solution for persistent data storage.”To generate a summary view of where Docker volumes are located when running Windows Subsystem for Linux (WSL) using Docker Desktop, we first need to understand the concept of how Docker interacts with WSL. The docker volumes are actually stored on your local machine’s hard drive and not in the WSL file system.
The Docker Desktop for Windows uses Linux containers on Windows (LCOW) and places it’s Docker volumes in a directory path, generally found at
C:\Users\[Your User Name]\AppData\Local\Docker\wsl\data-ext4.vhdx
or
%APPDATA%\Docker\wsl\data-ext4.vhdx
. Note that this is a VHDX file, which stands for Virtual Hard Disk format that is used by Windows for virtual machines. This VHDX file is where the Docker WSL data resides.
Here’s a table representing the generated summary:
Element
Description
Data Location in Docker Desktop for Windows
C:\Users\[Your User Name]\AppData\Local\Docker
VHDX File Name
wsl\data-ext4.vhdx
What’s inside the VHDX?
The Docker WSL data resides here
The aforementioned information shows that locating Docker volumes while using Docker Desktop with WSL is fundamentally tied up with understanding the way Docker establishes its communication and storage within the hosting environment. The Docker volumes’ actual location lies outside the Linux VM created by WSL, instead, they are part of your Windows file system. Therefore, interacting with Docker volumes within WSL involves navigating through the path mappings betweenWindows and WSL.
Thus, when you’re running WSL with Docker Desktop, you’re essentially accessing Docker volumes indirectly – Docker volume data exists on your Windows hard drive while being accessed and manipulated within your Linux VM. It’s a complex integration but gives us the versatility of working in a Linux environment with the underlying support of a Windows system.
For further reading, I would highly recommend looking into the Docker and WSL documentation provided on their official websites, both of which offer comprehensive coverage on these topics:
Understanding Docker volumes and their location, particularly when using WSL (Windows Subsystem for Linux) with Docker Desktop, can initially come across as challenging. But do not worry. Let’s break it down!
Docker volumes are the go-to method for persistent data provision and sharing between containers in Docker, bypassing the ephemeral nature of containers. Docker volumes exist outside traditional union filesystem and have several advantages:
They are efficient both for (I/O) operations and storage.
Data persists beyond the lifecycle of individual containers.
Information stored on volumes is easily shared and accessed by multiple containers.
On Docker Desktop for Windows installations, the location of your Docker volumes can differ depending on whether you’re using a Linux or Windows container. For instance, if you create a volume without specifying a source, it’ll be added to the default directory:
<docker installation path>/volumes/<volume name>
To locate Docker volumes when running WSL2 (Windows Subsystem for Linux 2) using Docker Desktop, you first need to understand that Docker Desktop stores Linux-related files inside a utility VM (Virtual Machine). By default, you cannot access this VM via more traditional methods like you could other VMs.
However, Docker volumes can still be located through WSL2 using your preferred terminal or command line interface. You may navigate to the specified Docker volume storing system using a command similar to:
cd /mnt/wsl/docker-desktop-data/version-pack-data/community/docker/volumes
Remember, the path might change based on Docker’s internal organization or configurations.
With an understanding of Docker Volumes’ benefits and how to locate them when utilizing Docker Desktop close at hand, you’re now equipped to possibly harness and leverage these data structures in a way that complements your container-based workflow. Gaining such knowledge is crucial as a professional developer, and when you look under the hood a little, complexities surrounding Docker volumes decrease considerably.
It’s always recommended for coders to delve into official Docker documentation whenever unsure about implementation specifics or best practices. The person behind the code can make all the difference!
The Windows Subsystem for Linux (WSL) and Docker Desktop have a critical connection when it comes to running distributed applications on a Windows workstation. To fully understand where Docker Volumes are located in this setup, we first need to invest some time exploring the symbiotic relationship between WSL and Docker Desktop.
A Peek into WSL
WSL is an ingenious compatibility layer designed to enable the execution of Linux binary executables natively within Windows 10.
wsl --set-version Ubuntu-20.04 2
It effectively runs a GNU/Linux environment — complete with command-line interface, system utilities, and applications — directly on Windows, unmodified, without the overhead associated with using a traditional virtual machine or dual boot setup.
Docker Desktop’s Marriage with WSL
Docker Desktop for Windows is a Docker Community Edition (CE) application created by Docker Inc. This version of Docker Desktop uses WSL 2 (based on the Linux 4.19 kernel) to run its docker daemons instead of Moby VM which was used in the previous versions of Docker Desktop utilizing Hyper-V.
docker run -d -p 80:80 docker/getting-started
By integrating Docker Desktop with WSL, developers can benefit from a consistent, cross-platform experience. With Docker Desktop permissions tied specifically to your WSL installation, Docker containers act as if they were native apps on your work station.
Where oh Where Are My Docker Volumes?
When you properly integrate Docker with WSL, volume mounts work out of the box. In fact, any directory path that works with any command in WSL will serve equally well as a volume mount for docker.
In the above example, hello.html will be in ‘my-vol’ volume in ‘/app’ folder. Now, where exactly is this Docker Volume?
Generally, all Docker data, including volumes, gets stored within /var/lib/docker/ or equivalent directory path based on the OS you’re using. However, due to WSL-Docker integration, WSL controls the Linux namespace for Docker. Which means, even though Docker sees its volume inside /var/lib/docker/volumes/, from the host perspective, this corresponds to the Docker Desktop virtual hard disk storage location.source
This storage can be accessed in Windows through File Explorer -> Network -> wsl$. Provided your WSL & Docker Desktop configurations are correctly set up, your Docker bound volumes should rest within these directories. Keep in mind Docker stores only non-empty named and anonymous volumes while bind mounts may be flat files or even non-existent paths.
Understanding the delicate interplay between WSL and Docker Desktop helps us manage our workflow better and perform required operations, like accessing the Docker volumes, more efficiently.Docker volumes, when running in a WSL (Windows Subsystem for Linux) environment, are particularly intriguing as they make use of Docker’s inbuilt volume management system. These volumes provide a more flexible and effective medium for data persistence compared to bind mounts, which allows for efficient data access even if the container stops.
Locating Docker volumes in WSL can be a bit intricate because they aren’t placed in your regular Windows or WSL directories. Rather, they are situated in a virtual hard disk (ext4.vhdx) on Docker Desktop’s virtual machine. The following path typically represents the location:
When you navigate through these paths, you’ll find various folders named ambiguously according to their unique identifiers. Each folder aligns with each individual Docker volume that you have created. Inside these folders, you will locate your actual persistent data associated with your Docker containers.
However, bear in mind that interacting with files in this location from your Windows filesystem could potentially lead to issues with file metadata and permissions.
Working With Docker Volumes in WSL
Using the Docker CLI, you can create, list, delete, and manage the Docker volumes from the WSL terminal.
To create a new volume, use the following command:
docker volume create my_volume
Listing all existing volumes is done through this command:
docker volume ls
For removing a Docker volume:
docker volume rm my_volume
When running a Docker container in WSL while specifying a volume, the syntax should correspond to the following format:
docker run -v my_volume:/path/in/container -it Ubuntu bash
In this format, ‘my_volume’ signifies your Docker volume name and ‘/path/in/container’ refers to the path where this volume would mount inside the container.
A Useful Tip: Using Bind Mounts for File Access
For scenarios wherein direct and immediate file interaction is required between your Windows OS and Docker Containers, another feature known as bind mounts can be utilized. Here’s how you can do it while running a container:
docker run -v /c/Users/username/Documents/my_directory:/path/in/container -it Ubuntu bash
The ‘-v’ flag specifies the source directory on your host system and the target directory inside your container where the mount point should reside.
It’s crucial to note that Docker interprets Windows paths very literally. Therefore, the Windows drive has to be declared (/c/) instead of declaring C:\.
To gain a more thorough understanding of Docker volume intricacies while working within WSL environments, the official Docker documentation(source) comes in handy.That’s a great question! Understanding the location of Docker Volumes when using Docker Desktop on Windows Subsystem for Linux (WSL) is crucial for managing your data efficiently.
Like UNIX-based systems, Docker stores volumes within the
/var/lib/docker/volumes
directory. This is easy to find on a native UNIX system. However, in our case, as we’re using WSL with Docker Desktop on a Windows machine, things require a little more digging.
When running Docker Desktop, volumes are nestled within the Docker Desktop VM. The actual path is a hidden system folder in Windows, and most tools won’t show it by default.
We can access this information by typing the following command in the terminal:
shell
wsl -l -v
And you may see something like this:
shell
NAME STATE VERSION
* docker-desktop Running 2
docker-desktop-data Running 2
The
docker-desktop-data
is where the Docker Desktop VM stores volume data.
To browse this file system, we can use another command to list all files under
/var/lib/docker/volumes
:
shell
wsl -d docker-desktop ls /var/lib/docker/volumes
With extensive digging, you’ll see that Docker volumes’ real location is somewhere deep in Windows’ system folders, along these lines:
. But without specific drag-and-drop capability between the Windows host system and the Docker guest environment or capacity for translating the VHDX filesystem, accessing this directly isn’t recommended or even practical.
Such an indirect location has functional benefits. It protects your system integrity and security, ensuring buffered interactions between your containers and the raw power of your base OS.
If you need to probe more, consider mounting your desired Windows directories into the Docker containers. This strategy allows guests (containers) to read/write, creating a convenient interaction channel without jeopardizing safety, and also making managing volumes directly a lot easier.
To mount, use a command like:
docker run -v c:/Users/path-to-directory-on-windows:/app imageName
This instructs Docker to map a local filesystem mount to a path in the container (/app). Any changes made to this destination will be written back to the source directory.
Understanding how Docker handles volumes and where it actually locates them (in the context of WSL on Docker Desktop) helps us harmoniously manage both host and virtualized environments, improving all-around robustness and maintainability.When working in a WSL environment using Docker Desktop, the navigation of Docker volume locations can seem confusing. But once you get your bearings right, it becomes quite smooth and intuitive.
All the significant directories, such as volumes, are stored under a default docker-desktop-data VM instance on WSL controlled by Docker Desktop. The data is primarily located in `/var/lib/docker/`, but it’s not accessible from the WSL Linux distros directly due to the design intention to encapsulate the data and prevent accidental modification.
To navigate the Docker volumes:
Step 1: Access Docker Desktop Data Instance
Open a new WSL terminal and switch to the Docker Desktop Data instance with this command:
wsl -d docker-desktop-data
Step 2: Navigate to the Docker Directory
Once you are in the Docker Desktop instance, go to the Docker directory:
cd /var/lib/docker/
This specific location allows us to explore all sorts of Docker configurations, including volumes.
Step 3: Open Volumes Directory
Navigate to the volumes directory:
cd volumes
Within this directory, each folder correlates to a different Docker volume that exists within your system, named after the unique identifier that Docker assigns to each volume upon creation.
Important Note:
In case you have made configuration modifications for Docker-Desktop, like setting custom paths or changing the location for the Docker Desktop resources, the path will mirror these changes. More information on how the directory structure looks inside `/var/lib/docker` can be found on Docker’s official documentation.
A Word on Container Storage:
It’s also key to remember when using Docker with WSL that containers and images are stored separately under Docker virtual machines (docker-desktop and docker-desktop-data) rather than the specific WSL distribution.
Cyberdrk in their GitHub post, “Running Docker on WSL”, provides an excellent overview of where Docker stores container image files when running inside a WSL environment.
With a good understanding of these locations, you can maximise your productivity and efficiency when dealing with Docker volumes in a WSL environment!One of the main pillars of Docker technology is building amicable ecosystems for developers by taking two fundamental insights – volumes, which store data generated by and used by docker containers and images, which are lightweight and standalone executable packages. In Docker, these fundamentally contribute to containerization utility.
With Windows Subsystem for Linux (WSL) operating within Docker Desktop, here’s how they interplay:
Docker Images And Containers:
Docker employs a Union File System that allows layers of files to overlay. For instance,
FROM ubuntu:18.04
This docker image has multiple read-only layers and each directive creates a new layer.
The real magic happens when you initialize the Docker container from an image. It adds a thin, modifiable layer atop the Image’s read-only layers which makes the containers incredibly lightweight.
Docker Volumes and Docker Containers:
When you create a Docker container, any data that the container generates will vanish when the container is deleted unless you use Docker volumes. These are preferred mechanisms that persist data generated and used by Docker containers.
So essentially, Docker volumes can be shared among multiple containers and their content exists as long as the volume exists.
To illustrate this, we can run a basic alpine based Docker container with a volume named ‘vol’.
docker run -it --name=alpine-test -v vol:/root/data alpine sh
Now, any data inside ‘/root/data’ in the container will remain even if the container is deleted, thanks to ‘vol’. This makes Docker volumes critical for data persistence.
Understanding Docker Device Mapper in WSL:
In a Docker on Linux setup, the Docker daemon directly interacts with the system. However, when using Docker Desktop on Windows, it uses a virtual machine (Hyper-V or WSL2 based) to build and run Docker containers, meaning Docker isn’t interfacing directly with Windows File System but rather through a Linux VM.
When operating within WSL using Docker Desktop, the space that Docker reserves for images, containers, volumes etc., is managed by Docker’s device mapper storage driver.
As shown above, the device mapper divides the physical storage into multiple logical blocks called ‘Data Blocks’. Each block corresponds to a single layer of a Docker image or container. Volume data gets propagated over these blocks as well.
This ‘Data-Block Pool’, where your Docker bits reside in, can be controlled using the preferences of Docker Desktop.
Locating Docker Volumes in WSL:
However, finding whether your ‘Data Block Pool’ lies isn’t really straightforward in Windows. If you’re using the new WSL2 backend (available in Docker Desktop 2.x), your volumes are stored in the distro’s ext4 vhd file at:
\\wsl$\«distro»\var\lib\docker\volumes
Where «distro» would be your running distro like ‘Ubuntu-20.04’.
The ‘\\wsl$\’ approach allows accessing your WSL Linux files in Windows explorer which makes management easier.
Ultimately, understanding the interlink between volumes, containers, and images and where they are located in Docker, particularly when using WSL, is essential to make the most out of Docker’s powerful containerization utility.When running WSL (Windows Subsystem for Linux) with Docker Desktop, the concept of data persistence is definitely something worth understanding to ensure that your applications and services continue to function as expected even after you close, reopen, or modify containers—or even reboot your system completely. One way this data persistence is achieved in Docker is by using “volumes”, which can be shared and reused among different containers.
So, where are these Docker volumes located when we run Docker on a WSL environment? They actually reside within the virtualized hard disk controlled by Docker Desktop. This location isn’t typically designated within the WSL filesystem but rather inside Docker’s own managed area.
Type
Location
Docker volume
/var/lib/docker/volumes/…
This path ‘/var/lib/docker/volumes/’ is where the majority of Docker volumes can be found when running Docker Desktop on a WSL environment. Each directory in this path corresponds to a particular volume mounted by a container. Although it appears to be a standard Unix filesystem path, remember that behind the scenes, the WSL and Docker Desktop are managing this area themselves, so consider it a specialized environment.
For retrieval and interaction with the data of Docker volumes on a larger scale, Docker’s CLI (Command Line Interface) provides commands such as
docker volume ls
To list all currently registered Docker volumes
And
docker volume inspect [volume_name]
This command gives detailed information about a specific volume including its location.
While working with Docker Desktop and WSL, throughout time, you’d possibly gain large volumes containing varying types of application-related data. It becomes necessary then to manage and monitor these volumes effectively. A wealth of open-source tools like Portainer and monitoring solutions such as Datadog exist allowing you to interact with and visualize your Docker volumes. And whilst running WSL, don’t forget the power of simple, built-in Linux commands such as ‘du -sh’ to check the usage size of a folder or volume at any time.
In short, Docker volumes through Docker desktop with WSL give developers a robust and consistent method for handling data persistence across various scenarios, irrespective of the container state. The combination makes a compelling case for developing and running Docker-infused applications right from your Windows workstation.
References:
1. Docker Documentation: Use volumes
2. Microsoft: About the Windows Subsystem for LinuxThe Docker’s data volumes are a crucial part of Docker infrastructure, offering persistent and sharable storage model for Docker containers. It’s essential to recognize where these volumes exist so you can manage them effectively.
When using Docker on Windows through Docker Desktop, the volume information is all stored within the Virtual Machine that Docker Desktop provisions. However, it is imperative to note that this VM exists in a hyper-abstracted state and doesn’t mount directly onto your Windows filesystem.
That being said, most modern Docker Desktop implementations lean towards WSL 2-based backend. Here’s a simple way to find Docker Volumes when running WSL using Docker Desktop:
The location of Docker volumes for Docker Desktop in a Windows environment with WSL 2 usually resides under the Linux file system at:
/var/lib/docker/volumes
You can navigate to this folder using the command-line (CLI) in Windows Subsystem for Linux (WSL). Simply open your favorite Linux distribution (Ubuntu, Debian, etc.) on WSL and enter the following command:
cd /var/lib/docker/volumes
There, you will have access to directories correlating to each existing Docker volume. You may require root user permissions to access or modify the files under these directories, however.
It’s important to remember that managing Docker volumes often involves interactions with the Docker engine, typically via Docker CLI commands. For instance:
* Listing all volumes:
$ docker volume ls
* Creating a volume:
$ docker volume create my-vol
* Examining a volume:
$ docker volume inspect my-vol
* Removing a volume:
$ docker volume rm my-vol
Though accessing the file system directly gives an operational level control, interfacing via the Docker engine commands helps ensure a greater consistency and less chance for unwanted side-effects.
I mustn’t ignore to mention the excellent documentation of Docker volumes available at Docker’s official website, where you can find detail insights about volume management in Docker environments.
Remember, Docker Desktop on Windows with its partnership with the Windows Subsystem for Linux simplifies much of this process, providing a more native-feeling Docker experience for Windows. Working together, they strive to maintain Docker’s principle of “Build, Ship, and Run Any App, Anywhere.”<
The impact of mount points in locating your Docker volume is significant, especially when running Windows Subsystem for Linux (WSL), using Docker Desktop. In a Docker file system, a mount point is where the data volume is mounted in the container. Mount points can significantly affect where and how you find your Docker volumes on WSL using Docker Desktop.
To brief it up, Docker offers persistent storage through the use of volumes. Docker volumes hold writable disk areas that are separate from the default Union File System. They enable data to persist even after a container stops. But finding these volumes becomes slightly complex.
Typical Location of Docker Volumes
In a typical non-WSL setup, Docker volumes are often located at
/var/lib/docker/volumes/
. For example, if you create a volume named myvolume, its data will be stored in
/var/lib/docker/volumes/myvolume/_data
.
# example
docker volume create myvolume
docker run -d -v myvolume:/container/path --name myContainer myImage
Locating Docker Volumes with WSL Using Docker Desktop
However, once we introduce WSL into the equation, locating Docker volumes changes entirely. Since Docker Desktop uses a virtual machine behind the scenes, your Docker volumes are not found in the traditional spot within the WSL filesystem.
Instead, your Docker volumes are stored inside the Docker Desktop Linux VM which Windows doesn’t have direct access to. If you’re looking for your volumes within WSL, this could lead to confusion and difficult debugging processes. Thus, it’s important to remember this change when running WSL with Docker Desktop.
Accessing Your Docker Volumes
Although your volumes might seem out of reach due to this structure change, there’s a way to access them without needing to mess around with the underlying VM. You need to use the
docker cp
command to copy files between the Docker container and the host file system.
# Copy a file from docker container to host
docker cp <containerId>:/file/path/within/container /host/path/to/copy/file/to
# Copy a file from host to docker container
docker cp /host/path/to/copy/file/from <containerId>:/file/path/within/container
While slightly more convoluted than just accessing a directory in your filesystem, this method provides a secure and reliable way of interacting with your Docker volumes within the WSL environment.
So, the mount points do indeed have an impact on locating your Docker volumes, especially when it comes to running WSL with Docker Desktop.
They make accessing the volumes directly seemingly impossible. Understanding how to navigate it saves time and prevents inevitable frustrations. Remember to use the docker commands wisely to interact with your data.
When you’re operating in a Windows environment and using the Windows Subsystem for Linux (WSL), working with Docker Volumes can be somewhat different compared to a traditional Linux environment. There are several points that need to be noted.
Docker Volumes Location
First and foremost, the location of Docker volumes might feel a little bit strange if you are used to Linux systems. In Windows environments, Docker Desktop stores Linux files inside a virtual hard disk (VHD). This VHD is labeled as “ext4.vhdx” and it’s typically found within your user directory under:
Docker\wsl\data\ext4.vhdx
. If you navigate into this file from your Windows Explorer, however, you will not find anything recognizable because it’s a specific type of Virtual Hard Drive containing an ext4 file system, which is a standard file system for most Linux distributions.
Operating System
Docker Volumes Path
Windows 10 (With WSL)
C:\users\your_username\Docker\wsl\data\ext4.vhdx
In order to view or manipulate files within these Docker volumes, you have to go through Docker Desktop’s WSL interface. On your terminal, you can do so by typing in:
wsl -d docker-desktop
command. Now, your terminal should be within the Docker instance of WSL. The function of Docker volumes still remains the same, meaning they store data generated by and used by Docker containers.
wsl -d docker-desktop
cd /var/lib/docker/volumes/
ls
The
/var/lib/docker/volumes/
path in your shell is where you’ll find all the Docker volumes for your containers. Every Docker volume is identified by a long alphanumeric string, which corresponds to a folder within this directory.
Volume Operations
Other Docker operations such as creating, deleting, and managing Docker volumes fall under the same Docker CLI commands whether on the console, terminal, or CMD.
Create a Docker volume.
docker volume create my_volume
List Docker volumes.
docker volume ls
Delete a Docker volume.
docker volume rm my_volume
Moving Data Between Windows and Docker
Sometimes, you may want to share files between your Windows environment and Docker containers. To accomplish this, you are advised to use Docker bind mounts. Bind mounts will have access to the file system path you point towards. Hence, you can easily move data around your local machine and Docker containers seamlessly. Do note that bind mounts rely heavily on your file system’s pathing. Here’s an example of how a Docker container can start and have a shared directory with your local system:
docker run -d --name=my_container -v C:/Users/Your_user/Documents:/shared_folder my_image
This command mounts the host directory,
C:/Users/Your_user/Documents
, to the container under the path
/shared_folder
.
Synchronization
Relying on Docker Desktop’s WSL 2 backend will greatly enhance your Docker experience on Windows. Since it works towards synchronization between Linux and Windows, Docker changes made within WSL will reflect on your Docker Desktop dashboard immediately and vice versa.
Your Responsibility
As with any tool, the main pointers revolve around understanding core functionalities and best practices. Read up on and keep close tabs on the versions and capabilities of both Docker and WSL updates. Microsoft and Docker are continually enhancing these tools and new versions may substantially streamline your Docker volume management and overall containerization tasks on Windows.
References:
1. Docker Documentation: https://docs.docker.com/
2. Microsoft WSL Documentation: https://docs.microsoft.com/en-us/windows/wsl/ Analyzing and understanding the location of Docker volumes when running WSL using Docker Desktop is an essential aspect for any developer working with such configuration. Docker Desktop for Windows uses WSL 2 to run its containers, thus resulting in storing its data as part of the Linux filesystem.
Typically, your Docker volumes, which serve as the designated locales for data persistency, reside within the
/var/lib/docker/volumes/
the directory inside your Docker virtual machine. This data storage mechanism assures you can consistently access and manage your data across various container life cycles.
Docker Volume Location
/var/lib/docker/volumes/
However, given Docker’s compatibility with the WSL filesystem, you might wonder how this impacts the storage positioning in the mixed environment. When it comes to WSL2, the Docker filesystem symmetry is maintained. Consequently, the Docker Desktop volumes when running on Windows Subsystem for Linux (WSL) remain at the same location, within the Linux system, stored under the
/var/lib/docker/volumes/
.
But remember that these directories are not directly accessible from the Windows host filesystem. So, to access or navigate these files from Windows, utilize a Linux command-line interface, such as the built-in one in WSL, or you’ll also find Docker volume inspection commands rather useful.
Having adequate knowledge about Docker’s structures, like volumes, is crucial because they form the nuts and bolts of containerization. As a coder, whether you are developing, testing, or deploying applications using Docker and WSL, this comprehension definitely improves your efficiency while handling data persistence and storage structures.
It’s also worth noting that Docker continues to evolve to offer more seamless integration to its users among diverse environments. Keeping track of Docker’s updates, especially those relating to these key aspects, helps you adapt to potential changes quickly.
To dive deeper into understanding docker volumes management, consider reading the official Docker documentation [link]. It will allow you to uncover more detailed insights about managing docker volumes, including exploring different docker volume drivers, and managing volumes through docker CLI commands effectively.
Gamezeen is a Zeen theme demo site. Zeen is a next generation WordPress theme. It’s powerful, beautifully designed and comes with everything you need to engage your visitors and increase conversions.
