---
title: Common Issues with Docker
description: "Running Namazu Elements locally is best done in [Docker](https://namazustudios.com/glossary/docker/). We provide [Community Edition](https://github.com/NamazuStudios/docker-compose/) as a pre-configured environment using [Docker Compose](https://docs.docker.com/compose/). If you are running into trouble using [Docker](https://namazustudios.com/glossary/docker/), this page has a few common problems and solutions. ## Not in…"
url: "https://namazustudios.com/docs/troubleshooting-guide/community-edition/common-issues-with-docker/"
updated: "2026-08-13"
category: Troubleshooting / Namazu Elements Community Edition
---

# Common Issues with Docker

Running Namazu Elements locally is best done in [Docker](https://namazustudios.com/glossary/docker/). We provide [Community Edition](https://github.com/NamazuStudios/docker-compose/) as a pre-configured environment using [Docker Compose](https://docs.docker.com/compose/). If you are running into trouble using [Docker](https://namazustudios.com/glossary/docker/), this page has a few common problems and solutions.

## Not in the Correct Working Directory

[Docker](https://namazustudios.com/glossary/docker/) relies on the current working directory for almost all operations. Typically you will see errors about missing configuration if you do not `cd` to the correct directory first.

```
ptwohig@ryzen:~$ docker compose up -d
no configuration file provided: not found
```

If you are using [Github Desktop](https://desktop.github.com/download/), then look for your project in these directories:

- Windows - `C:Users<your-username>DocumentsGitHub`
- Mac OS - `~/Documents/GitHub`

Refer to the usage for your specific git client when locating the directory on disk. Before running [Docker](https://namazustudios.com/glossary/docker/), ensure you are in the correct directory.

```
cdC:Usersusername<your-userGitHubdocker-compose
```

## [Docker](https://namazustudios.com/glossary/docker/) [Service](https://namazustudios.com/glossary/service/) Not Running

Not all operating systems immediately run [Docker](https://namazustudios.com/glossary/docker/) or the [Docker](https://namazustudios.com/glossary/docker/) [Service](https://namazustudios.com/glossary/service/) can be shut down indvertently. Typically errors like this will appear:

```
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```

```
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock
```

To fix this start [Docker](https://namazustudios.com/glossary/docker/) using the instructions for your operating system.

- Windows
  - **Desktop App:** Search for "[Docker](https://namazustudios.com/glossary/docker/) Desktop" in the **Start menu** and launch it.
  - **CLI:** Use the [Docker Desktop CLI](https://docs.docker.com/desktop/features/desktop-cli/) by running `Docker desktop start` in PowerShell or Command Prompt (requires [Docker](https://namazustudios.com/glossary/docker/) Desktop 4.37+).
  - **Auto-start:** In settings, check **"Start [Docker](https://namazustudios.com/glossary/docker/) Desktop when you log in"** to have it run on boot. 
- Mac
  - **Desktop App:** Open **[Docker](https://namazustudios.com/glossary/docker/).app** from your **Applications** folder or use Spotlight (`Cmd + Space`).
  - **CLI:** Run `open -a Docker` in the Terminal. For newer versions (4.37+), you can also use `Docker desktop start`.
  - **Headless/Alternative:** If using Colima, use the command `colima start`. 
- Linux
  - **Systemd (Standard Engine):** Start the daemon with `sudo systemctl start Docker`. To ensure it starts on every boot, use `sudo systemctl enable Docker`.
- [Docker](https://namazustudios.com/glossary/docker/) Desktop for Linux
  - **GUI:** Launch "[Docker](https://namazustudios.com/glossary/docker/) Desktop" from your [Application](https://namazustudios.com/glossary/application/) menu (Gnome/KDE).
  - **CLI:** Use `systemctl --User start Docker-desktop` to start the desktop-managed engine.