Hi!
I am getting the following log entries a lot on v1.3.2:
newt | INFO: 2025/07/14 09:12:34 Received Docker socket check request
newt | INFO: 2025/07/14 09:12:34 Docker socket path is not set
newt | INFO: 2025/07/14 09:12:35 Received Docker socket check request
newt | INFO: 2025/07/14 09:12:35 Docker socket path is not set
newt | INFO: 2025/07/14 09:12:35 Received Docker socket check request
newt | INFO: 2025/07/14 09:12:35 Docker socket path is not set
I am wondering, is this supposed to happen on this version or not? According to this it's already opt-in, and I have the below, most simple compose setup, without any opt-ins:
What am I supposed to do to avoid these messages? Thanks.
Originally created by @wouldntyouknow on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/86
Hi!
I am getting the following log entries a lot on v1.3.2:
```
newt | INFO: 2025/07/14 09:12:34 Received Docker socket check request
newt | INFO: 2025/07/14 09:12:34 Docker socket path is not set
newt | INFO: 2025/07/14 09:12:35 Received Docker socket check request
newt | INFO: 2025/07/14 09:12:35 Docker socket path is not set
newt | INFO: 2025/07/14 09:12:35 Received Docker socket check request
newt | INFO: 2025/07/14 09:12:35 Docker socket path is not set
```
I am wondering, is this supposed to happen on this version or not? According to [this](https://github.com/fosrl/newt/pull/56) it's already opt-in, and I have the below, most simple compose setup, without any opt-ins:
```
services:
newt:
image: fosrl/newt:latest
container_name: newt
restart: unless-stopped
environment:
- PANGOLIN_ENDPOINT=https://[endpoint]
- NEWT_ID=[id]
- NEWT_SECRET=[secret]
```
What am I supposed to do to avoid these messages? Thanks.
u need docker path as volumes and environment i think ... lock at the Configuration on the readme ...
<!-- gh-comment-id:3068622129 -->
@skyzuma commented on GitHub (Jul 14, 2025):
u need docker path as volumes and environment i think ... lock at the Configuration on the readme ...
@wouldntyouknow commented on GitHub (Jul 14, 2025):
I get that, but that would be opting in, wouldn't it? What I would like to do is just continue using newt as before, without it wanting to do anything with docker socks.
<!-- gh-comment-id:3068629299 -->
@wouldntyouknow commented on GitHub (Jul 14, 2025):
I get that, but that would be opting in, wouldn't it? What I would like to do is just continue using newt as before, without it wanting to do anything with docker socks.
@oschwartz10612 commented on GitHub (Jul 14, 2025):
Yeah you can safely ignore these messages. Its just ignoring the docker requests because the path is not set. I will make the log messages debug so as not to confuse people in the future!
<!-- gh-comment-id:3070337935 -->
@oschwartz10612 commented on GitHub (Jul 14, 2025):
Yeah you can safely ignore these messages. Its just ignoring the docker requests because the path is not set. I will make the log messages debug so as not to confuse people in the future!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @wouldntyouknow on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/86
Hi!
I am getting the following log entries a lot on v1.3.2:
I am wondering, is this supposed to happen on this version or not? According to this it's already opt-in, and I have the below, most simple compose setup, without any opt-ins:
What am I supposed to do to avoid these messages? Thanks.
@skyzuma commented on GitHub (Jul 14, 2025):
u need docker path as volumes and environment i think ... lock at the Configuration on the readme ...
@wouldntyouknow commented on GitHub (Jul 14, 2025):
I get that, but that would be opting in, wouldn't it? What I would like to do is just continue using newt as before, without it wanting to do anything with docker socks.
@oschwartz10612 commented on GitHub (Jul 14, 2025):
Yeah you can safely ignore these messages. Its just ignoring the docker requests because the path is not set. I will make the log messages debug so as not to confuse people in the future!