如何从Docker容器获取Haproxy日志？附相关配置信息

Hey there! Let's walk through how to pull logs from your Docker-run HAProxy, since you already have logging configured in your haproxy.config (nice job setting those local0 and local1 targets!). Here are a few practical methods to get the logs you need:

Method 1: Check Docker's Built-In Logs (Quick Win) #

If your HAProxy is configured to output logs directly to stdout/stderr (or if the container's syslog forwards them there), you can skip straight to Docker's native log commands:

• To stream logs in real-time: docker logs -f <your-haproxy-container-id-or-name>
• To view the last 100 lines (adjust the number as needed): docker logs --tail 100 <your-haproxy-container-id-or-name>

Method 2: Work with Your Existing Syslog Configuration #

Your current global section sends logs to the local syslog's local0 (all levels) and local1 (notice level). To capture these, you have two options:

Option A: Redirect HAProxy Logs to a File (Simpler) #

If you don't want to mess with syslog services, tweak your haproxy.config to write logs directly to a file:

global
  log 127.0.0.1 local0
  log 127.0.0.1 local1 notice
  log /var/log/haproxy/haproxy.log local0 info  # Add this line to log to a file

Save the config, then restart your HAProxy container: docker restart <your-haproxy-container-id-or-name>

Now you can either:

• Jump into the container to view logs:

  docker exec -it <your-haproxy-container-id-or-name> /bin/bash
  tail -f /var/log/haproxy/haproxy.log
  

• Or mount the log directory to your host (more on that in Method 3) to avoid entering the container every time.

Option B: Set Up Rsyslog in the Container (Match Your Original Config) #

If you want to stick with the syslog targets you already defined, install and configure rsyslog inside the container to catch those logs:

1. First, install rsyslog in the container:

   docker exec -it <your-haproxy-container-id-or-name> apt update && apt install -y rsyslog
   

2. Create a rsyslog config file for HAProxy at /etc/rsyslog.d/haproxy.conf:

   $ModLoad imudp
   $UDPServerRun 514
   # Route local0 logs to a main haproxy log file
   local0.* /var/log/haproxy/haproxy.log
   # Route local1 notice logs to a separate file
   local1.notice /var/log/haproxy/haproxy-notice.log
   

3. Create the log directory and fix permissions so rsyslog can write to it:

   docker exec -it <your-haproxy-container-id-or-name> mkdir -p /var/log/haproxy && chown syslog:adm /var/log/haproxy
   

4. Restart rsyslog to apply the changes:

   docker exec -it <your-haproxy-container-id-or-name> service rsyslog restart
   

5. Now you can view the logs either inside the container or via a host mount. For real-time viewing:

   docker exec -it <your-haproxy-container-id-or-name> tail -f /var/log/haproxy/haproxy.log
   

Method 3: Mount Logs to Your Host (Convenient Long-Term) #

To avoid jumping into the container every time you need logs, mount the container's log directory to your host machine when you start HAProxy. This way, logs are saved directly on your host:

When starting the container (adjust paths to match your setup):

docker run -d \
  --name haproxy \
  -v /path/on/your/host/haproxy/config:/etc/haproxy \  # Mount your config file
  -v /path/on/your/host/haproxy/logs:/var/log/haproxy \  # Mount log directory to host
  haproxy:latest

Now you can view logs directly from your host:

tail -f /path/on/your/host/haproxy/logs/haproxy.log

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