Running Namazu Elements locally is best done in Docker. We provide Community Edition as a pre-configured environment using Docker Compose. If you are running into trouble using Docker, this page has a few common problems and solutions.
Not in the Correct Working Directory #
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, then look for your project in these directories:
- Windows –
C:\Users\<your-username>\Documents\GitHub - Mac OS –
~/Documents/GitHub
Refer to the usage for your specific git client when locating the directory on disk. Before running Docker, ensure you are in the correct directory.
cdC:\Users\username\<your-User\GitHub\Docker-compose
Docker Service Not Running #
Not all operating systems immediately run Docker or the Docker 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 using the instructions for your operating system.
- Windows
- Desktop App: Search for “Docker Desktop” in the Start menu and launch it.
- CLI: Use the Docker Desktop CLI by running
Docker desktop startin PowerShell or Command Prompt (requires Docker Desktop 4.37+). - Auto-start: In settings, check “Start Docker Desktop when you log in” to have it run on boot.
- Mac
- Linux
- Docker Desktop for Linux
- GUI: Launch “Docker Desktop” from your Application menu (Gnome/KDE).
- CLI: Use
systemctl --User start Docker-desktopto start the desktop-managed engine.

