Hello everyone,
I’m new to Docker, but I’m having trouble getting started right from the start. I installed the Docker Desktop App version 4.36.0 on my Mac Mini. After installation, I wanted to install the portainer-ce application.
The installation initially went smoothly. portainer-ce can be reached via the port in Safari. However, no Docker environment can be found.
The error message in the log files is "WRN github.com/portainer/portainer/api/platform/platform.go:70 > failed to retrieve docker info | error=“Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?”
Using the terminal command docker info, I get the next warning message WARNING: daemon is not using the default seccomp profile.
Both MacOS and Docker are freshly installed and no settings have been made. How can this error be resolved?
To check whether it was me or my system, I tried the same thing on my brother’s Macbook Pro and also got the same error. The Docker app was also installed on the Macbook Pro and an attempt was made to get Portainer to run. Same warning.
Could it be possible that it is a bug in the Docker Desktop App?
Everything is possible, but I can say annoying “it works on my machine” What I’m curious about is how you installed Portainer.Did you install it directly on macOS or used the Docker Desktop extension in Docker Desktop? I can’t imagine how the extension would fail.
Hallo rimelek,
thanks for your reply.
I try to install portainer-ce as a container in the Docker Desktop App, because i want to access to the page over the browser.
docker context ls
NAME DESCRIPTION DOCKER ENDPOINT ERROR
default Current DOCKER_HOST based configuration unix:///var/run/docker.sock
desktop-linux * Docker Desktop unix:///Users/minihome/.docker/run/docker.sock
And this is the log from the portainer-ce container
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:370 > encryption key file not present | filename=portainer
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:393 > proceeding without encryption key |
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/database/boltdb/db.go:125 > loading PortainerDB | filename=portainer.db
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/internal/ssl/ssl.go:80 > no cert files found, generating self signed SSL certificates |
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/chisel/service.go:228 > generated a new Chisel private key file | private-key=/data/chisel/private-key.pem
2024-12-08 17:03:33 2024/12/08 16:03:33 server: Reverse tunnelling enabled
2024-12-08 17:03:33 2024/12/08 16:03:33 server: Fingerprint z3ZHzs22ydc6cOHNdP3IcpgShkgYucKtPhnlIFZmJS4=
2024-12-08 17:03:33 2024/12/08 16:03:33 server: Listening on http://0.0.0.0:8000
2024-12-08 17:03:33 2024/12/08 04:03PM WRN github.com/portainer/portainer/api/platform/platform.go:70 > failed to retrieve docker info | error="Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:655 > starting Portainer | build_number=120 go_version=go1.21.13 image_tag=linux-arm64-2.21.4 nodejs_version=18.20.4 version=2.21.4 webpack_version=5.88.2 yarn_version=1.22.22
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/http/server.go:370 > starting HTTPS server | bind_address=:9443
2024-12-08 17:03:33 2024/12/08 04:03PM INF github.com/portainer/portainer/api/http/server.go:354 > starting HTTP server | bind_address=:9000
2024-12-08 17:08:33 2024/12/08 04:08PM INF github.com/portainer/portainer/api/adminmonitor/admin_monitor.go:62 > the Portainer instance timed out for security purposes, to re-enable your Portainer instance, you will need to restart Portainer |
Update: i tried the Portainer extension and it is working. But is it possible to access the extension from the browser?
If the extension works anf your context is right, you probably forgot to mount the socket to the container. Starting from the official image’s description on Docker Hub, you can find the documentation with example commands to create a portainer container with the unix socket mounted
What I’m curious about is how you installed Portainer.Did you install it directly on macOS or used the Docker Desktop extension in Docker Desktop? I can’t imagine how the extension would fail.