When trying to start the Exploratory Server (On-Premise), it fails with an error such as "Cannot connect to the Docker daemon” or “permission denied while trying to connect to the Docker daemon”

Kei_Saito · May 15, 2025, 5:53pm

If you see errors such as “Cannot connect to the Docker daemon” or “permission denied while trying to connect to the Docker daemon” when trying to start the Exploratory server (On-Premise), it is possible that the Docker service is not running. Please follow the steps below to start the Docker service, then try starting the Exploratory server again.

Step 1: Check if the Docker service is running

First, check whether Docker is currently running:

docker info

If the information is displayed correctly, the Docker service is running.
If you see an error such as Cannot connect to the Docker daemon..., it is likely that Docker is not running.

Step 2: Check if Docker is installed via snap

snap list | grep docker

If there is any output, Docker is installed via snap.
If nothing is returned, Docker may be installed using a standard package manager such as apt or yum instead of snap.

Step 3A: If Docker is installed via snap

Check the status of the snap service:
```
sudo snap services docker
```
Start Docker:
```
sudo snap start docker
```
Enable Docker to start automatically (if needed):
```
sudo snap enable docker
```
Confirm Docker is running:
```
docker info
```

Step 3B: If Docker is not installed via snap (using systemd)

Check the status of the Docker service:
```
systemctl status docker
```
Start Docker:
```
sudo systemctl start docker
```
Enable Docker to start automatically (if needed):
```
sudo systemctl enable docker
```
Confirm Docker is running:
```
docker info
```