Docker socket suddenly not working anymore while it is in the container correctly #3609
Replies: 7 comments 1 reply
-
|
The errors don't show anything that is obvious to me what could be wrong. The deadline exceeding suggests something is wrong with Docker. There was a similar issue not too long at #3600. I didn't know what was wrong either. The author nuked everything and it started working. Similar error as yours. I wouldn't be able to help you much since I don't have a Windows machine. Hopefully, you can investigate this error. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @amir20 , I have a Mac desktop installed. They released an update for Docker Desktop, and after installing today's update and restarting Docker, Dozzle couldn't start up. I'm getting the same error. |
Beta Was this translation helpful? Give feedback.
-
|
I think #3600 (comment) is what fixed it. I use Orbstack on Mac so it hasn't happened to me yet. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Will try
…On Thu, Feb 6, 2025 at 9:11 PM Amir Raminfar ***@***.***> wrote:
I think #3600 (comment)
<#3600 (comment)> is
what fixed it. I use Orbstack on Mac so it hasn't happened to me yet.
—
Reply to this email directly, view it on GitHub
<#3606 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKC2OLS5RXAVLYM3CDBCFJT2OO6YRAVCNFSM6AAAAABWTJNYSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBQHA4TKOJYHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
With kind regards/Met vriendelijke groeten,
Jur Braam
Senior Software Engineer
EyeQuestion Software - Logic8 BV - Nieuwe Aamsestraat 90D - 6662 NK - Elst
(Gld) - The Netherlands
T +31 (0)481 350370 | USA T +1 513 822 4705 | M +31 (0)6 1053 4507 | E
***@***.***
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
entity to whom it is addressed and others authorised to receive it. If you
are not the intended recipient you are hereby (a): notified that any
disclosure, copying, distribution or taking any action with respect to the
content of this information is strictly prohibited and may be unlawful, and
(b): kindly requested to inform the sender immediately and destroy any
copies. Logic8 BV does neither accept any responsibility and/or liability
for the improper and incomplete transmission of the information contained
in this communication nor for any delay in its receipt.
|
Beta Was this translation helpful? Give feedback.
-
|
Moving this to a discussion. If anybody find a better way then let me know here. |
Beta Was this translation helpful? Give feedback.
-
|
I spent the entire Saturday afternoon and part of Monday trying to identify the cause of the issue, but without success. I checked whether it could be related to the Docker process, permissions, or other factors, but I encountered the same problem with Docker Desktop. Everything was working fine until recently; I also tried using a previous version of Dozzle, but the issue persists. It turns out to be a malfunction caused by the latest Docker Desktop update. After installing and testing OrbStack, Dozzle started working correctly again. |
Beta Was this translation helpful? Give feedback.
-
|
That is right. Desktop introduced a bug. This should be fixed now though on my side where I provide the right headers. I have also increased the timeout to 10s. Not much more I can do. See the pinned bug #3610 |
Beta Was this translation helpful? Give feedback.
-
|
Your fix with uninstalling docker through the guide, deleting all the
folders and installing it again worked for me. Everything works fine now!
Thanks
With kind regards/Met vriendelijke groeten,
Jur Braam
Senior Software Engineer
EyeQuestion Software - Logic8 BV - Nieuwe Aamsestraat 90D - 6662 NK - Elst
(Gld) - The Netherlands
T +31 (0)481 350370 | USA T +1 513 822 4705 | M +31 (0)6 1053 4507 | E
***@***.***
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
entity to whom it is addressed and others authorised to receive it. If you
are not the intended recipient you are hereby (a): notified that any
disclosure, copying, distribution or taking any action with respect to the
content of this information is strictly prohibited and may be unlawful, and
(b): kindly requested to inform the sender immediately and destroy any
copies. Logic8 BV does neither accept any responsibility and/or liability
for the improper and incomplete transmission of the information contained
in this communication nor for any delay in its receipt.
Op do 13 feb 2025 om 20:49 schreef Amir Raminfar ***@***.***>
… That is right. Desktop introduced a bug. This should be fixed now though
on my side where I provide the right headers. I have also increased the
timeout to 10s. Not much more I can do. See the pinned bug #3610
<#3610>
—
Reply to this email directly, view it on GitHub
<#3609 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKC2OLRMTJMC3WI2CWMLFMT2PTZKZAVCNFSM6AAAAABXC7XD2WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJZGIYTINY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
🔍 Check for existing issues
How is Dozzle deployed?
Standalone Deployment
📦 Dozzle version
8.10.6
✅ Command used to run Dozzle
name: eq-server-tools
networks:
eq-tools-net:
name: eq-tools-net
driver: bridge
services:
Docker logs monitoring tools
logs-viewer:
container_name: eq-server-tools-logs-viewer
hostname: eq-logs-viewer
restart: always
profiles: [ logs-viewer ]
pull_policy: always
user: 0:0
image: amir20/dozzle:v8.10.6
environment:
DOZZLE_BASE: /logs
DOZZLE_AUTH_PROVIDER: ${DOZZLE_AUTH_PROVIDER}
DOZZLE_LEVEL: debug
DOZZLE_ENABLE_ACTIONS: true
DOZZLE_NO_ANALYTICS: true
networks:
- eq-tools-net
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./images/eq-nginx-image/users.yml:/data/users.yml
ports:
- 1337:8080
deploy:
resources:
limits:
memory: 500M
reservations:
memory: 500M
🐛 Describe the bug / provide steps to reproduce it
2025-02-06 12:20:53 {"level":"info","time":"2025-02-06T11:20:53Z","message":"Dozzle version v8.10.6"}
2025-02-06 12:20:53 {"level":"debug","filter":{},"host":"docker-desktop","time":"2025-02-06T11:20:53Z","message":"Listing containers"}
2025-02-06 12:20:56 {"level":"debug","error":"context deadline exceeded","time":"2025-02-06T11:20:56Z","message":"Could not connect to local Docker Engine"}
2025-02-06 12:20:56 {"level":"fatal","time":"2025-02-06T11:20:56Z","message":"Could not connect to any Docker Engine"}
Its not connecting to the docker socket anymore. I verified that the docker socket is actually mounted to /var/run/docker.sock and has permissions for root:root in the container. My docker daemon on my host machine (Windows with WSL2 Linux) is running and other containers are running fine.
💻 Environment
Client:
Version: 27.5.1
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Ask Gordon - Docker Agent (Docker Inc.)
Version: v0.7.3
Path: C:\Program Files\Docker\cli-plugins\docker-ai.exe
buildx: Docker Buildx (Docker Inc.)
Version: v0.20.1-desktop.2
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.32.4-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.38
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.4
Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: C:\Program Files\Docker\cli-plugins\docker-feedback.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scout: Docker Scout (Docker Inc.)
Version: v1.16.1
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 2
Server Version: 27.5.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Runtimes: nvidia runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc version: v1.1.12-0-g51d5e946
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.167.4-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 20
Total Memory: 15.46GiB
Name: docker-desktop
ID: 4c9b1b59-4725-4a63-8ed5-dfbfe9c7789b
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=npipe://\.\pipe\docker_cli
Experimental: true
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile
📸 If applicable, add screenshots to help explain your bug
No response
📜 If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.
2025-02-06 12:23:03 {"level":"fatal","time":"2025-02-06T11:23:03Z","message":"Could not connect to any Docker Engine"}
2025-02-06 12:24:03 {"level":"info","time":"2025-02-06T11:24:03Z","message":"Dozzle version v8.10.6"}
2025-02-06 12:24:03 {"level":"debug","filter":{},"host":"docker-desktop","time":"2025-02-06T11:24:03Z","message":"Listing containers"}
2025-02-06 12:24:06 {"level":"debug","error":"context deadline exceeded","time":"2025-02-06T11:24:06Z","message":"Could not connect to local Docker Engine"}
2025-02-06 12:24:06 {"level":"fatal","time":"2025-02-06T11:24:06Z","message":"Could not connect to any Docker Engine"}
Beta Was this translation helpful? Give feedback.
All reactions