How to Identify What's Accessing My Docker Network?
Asked by
CuriousTechie42
I'm trying to figure out if my devices are being hacked or if I'm just misinterpreting my logs. I have several web-facing servers like Immich and Glances, and I use Virtualmin for hosting websites. Everything is set up behind Traefik and mostly runs via Docker. Recently, I've noticed some log entries showing requests from an IP in my Docker internal network (192.168.57.1) to my Traefik server, specifically targeting port 10000 on my Virtualmin setup. My concern is that there doesn't seem to be a physical device corresponding to that IP, so I'm wondering if it's just Docker networking at play or if there's a potential intrusion. How can I determine whether this activity is normal or if something suspicious is happening?
Answers
Check your setup for any defined health checks. Sometimes, the Docker host will send requests to the web server it's hosting to verify that everything's up and running, which could explain the traffic you're seeing.
Reply to this answer
It sounds like that could be the Docker bridge doing its thing. Try running `ip addr | grep 192.168.57.1` to get more details, or inspect all your containers to see what's active on that network.
Reply to this answer
From what I can see, it looks like that IP might be a virtual router for your Docker network. It's not unusual to see traffic like this if everything is properly isolated but check to confirm its role.
Reply to this answer
Is your Virtualmin or Webmin at the helm of listening on port 10000? Theyโre both known to use that port. There might be a chance that there's an unresolved TLD on the server causing repeated requests.
Reply to this answer
What you're seeing seems to be a bad request directed at Traefik. Since itโs a GET request for `/`, and if you donโt have a route for it, itโs completely understandable. Itโs probably just bots or some random scripts trying to connect, nothing to worry about.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions