Windows环境Docker与Filebeat自动发现权限拒绝问题求助

Hey there, let's work through this permission issue you're facing with Docker and Filebeat on Windows. I've dealt with similar headaches before, so here are actionable solutions to get your autodiscover up and running:

1. Switch Filebeat to Use TCP Instead of Unix Socket (Recommended) #

Since you already enabled Docker's TCP daemon on tcp://localhost:2375, the easiest fix is to configure Filebeat to connect via this TCP endpoint instead of the Unix socket. This bypasses all the permission quirks of mounting /var/run/docker.sock on Windows.

Update your filebeat.yml autodiscover config to point to the Windows host's TCP port using host.docker.internal (a special DNS name in Docker for Windows that resolves to your host machine):

filebeat.autodiscover:
  providers:
    - type: docker
      host: "tcp://host.docker.internal:2375"
      # Keep your other autodiscover settings (like templates, hints, etc.) here

After updating, restart your Filebeat container and the permission error should vanish.

2. Run Filebeat Container as Root (Quick Test Fix) #

If you want to stick with the Unix socket mount, you can run the Filebeat container as the root user, which will have full access to the mounted /var/run/docker.sock.

Modify your docker-compose.yml to add the user directive:

filebeat:
  image: store/elastic/filebeat:7.3.0
  user: root  # Add this line to run as root
  volumes:
    - ./config/filebeat.yml:/usr/share/filebeat/filebeat.yml:ro
    - /var/lib/docker/containers/:/var/lib/docker/containers/:ro
    - /var/run/docker.sock:/var/run/docker.sock:ro

⚠️ Note: Running containers as root has security implications, so this is best for testing or non-production environments.

3. Fix WSL2 Permissions (If Using WSL2 Backend) #

If you're using Docker Desktop with the WSL2 engine, the /var/run/docker.sock file lives inside your WSL2 distribution. You need to ensure your WSL2 user is in the docker group to grant access:

1. Open your WSL2 terminal (e.g., Ubuntu for Windows)
2. Run this command to add your user to the docker group:

   sudo usermod -aG docker $USER
   

3. Log out and back into your WSL2 session, or restart WSL2 with:

   wsl --shutdown
   

4. Restart Docker Desktop to apply changes.

4. Verify TCP Daemon Accessibility #

Double-check that your Docker TCP daemon is actually reachable from within the container:

On your Windows host, open Command Prompt or PowerShell and run:

curl http://localhost:2375/v1.22/containers/json?limit=0

If you get a JSON response (even an empty array []), the TCP port is working. If you get an error, go back to Docker Desktop settings, confirm "Expose daemon on tcp://localhost:2375 without TLS" is checked, and restart Docker.

内容的提问来源于stack exchange，提问作者cdalxndr