从 haproxy:1.5-alpine 构建 haproxy 容器
( https://github.com/docker-library/haproxy/blob/1848d2933afbefd0e0a068dc7b5a753ab7842e6c/1.5/alpine/Dockerfile )
haproxy 容器开始正常,但是我如何实现详细的 haproxy 日志记录并将其定向到标准输出。
我的haproxy配置是
global
log /dev/log local0
# log /dev/log local1 notice
# chroot /var/lib/haproxy
# stats socket /run/haproxy/admin.sock mode 660 level admin
stats timeout 30s
user haproxy
group haproxy
daemon
tune.ssl.default-dh-param 2048
# Default SSL material locations
#ca-base /etc/ssl/certs
#crt-base /etc/ssl/private
ssl-default-bind-options no-sslv3
ssl-default-bind-ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM
enter code here
defaults
log global
mode http
option httplog
option dontlognull
# fixed configuration by Benson
option http-keep-alive
timeout http-keep-alive 5m
timeout http-request 5s
timeout connect 300s
timeout client 300s
timeout server 300s
timeout check 300s
#old configurations causing connection timeouts
#timeout connect 5000
#timeout client 50000
#timeout server 50000
errorfile 400 /usr/local/etc/haproxy/errors/400.http
errorfile 403 /usr/local/etc/haproxy/errors/403.http
errorfile 408 /usr/local/etc/haproxy/errors/408.http
errorfile 500 /usr/local/etc/haproxy/errors/500.http
errorfile 502 /usr/local/etc/haproxy/errors/502.http
errorfile 503 /usr/local/etc/haproxy/errors/503.http
errorfile 504 /usr/local/etc/haproxy/errors/504.http
balance roundrobin
option httpchk
我尝试了通过 docker entrypoint.sh 中的以下命令将日志定向到标准输出的选项
"/bin/sh -c/sbin/syslogd -O/dev/stdout"
#!/bin/sh
set -e
# first arg is `-f` or `--some-option`
if [ "${1#-}" != "$1" ]; then
set -- haproxy "$@"
fi
if [ "$1" = 'haproxy' ]; then
# if the user wants "haproxy", let's use "haproxy-systemd-wrapper" instead so we can have proper reloadability implemented by upstream
/bin/sh -c /sbin/syslogd -O /dev/stdout
shift # "haproxy"
set -- "$(which haproxy-systemd-wrapper)" -p /run/haproxy.pid "$@"
fi
exec "$@"
然而,当我通过 haproxy 浏览应用程序时,没有日志被注册,尽管它可以正常工作。
我想知道如何通过 alpine haproxy 容器内的 haproxy 获得详细的日志记录
最佳答案
您需要将/dev/log 从主机传递到容器中,然后从主机端读取您的日志! haproxy 的作者反对将日志记录到标准输出(出于性能原因),因此除了我所描述的(或在 pod 中的另一个容器中运行 syslog 守护程序)之外,您无能为力
关于docker - 如何在 haproxy :1. 5-alpine Docker 容器中获取日志,我们在Stack Overflow上找到一个类似的问题:https://stackoverflow.com/questions/44137797/