Downgrade haproxy image from latest to lts
Starting with the automated update to the haproxy 2.9.1 image at 04:00 today, we noticed the service immediately spiking up to 100% CPU and quickly filling its session table. Downgrading from the latest tag to lts (currently 2.8.5) appears to have solved it for now. This might be https://github.com/haproxy/haproxy/issues/2393 . Change-Id: I3085e7921f43665118678a660d777601f08debd3
This commit is contained in:
parent
88893cad0b
commit
f4a20b0502
@ -5,7 +5,7 @@ version: '2'
|
|||||||
services:
|
services:
|
||||||
haproxy:
|
haproxy:
|
||||||
restart: always
|
restart: always
|
||||||
image: docker.io/library/haproxy:latest
|
image: docker.io/library/haproxy:lts
|
||||||
# NOTE(ianw) 2021-05-17 : haproxy >= 2.4 runs as a non-privileged
|
# NOTE(ianw) 2021-05-17 : haproxy >= 2.4 runs as a non-privileged
|
||||||
# user. The main problem here is we use host networking, so the
|
# user. The main problem here is we use host networking, so the
|
||||||
# haproxy user is not allowed to bind to low ports (80/443). The
|
# haproxy user is not allowed to bind to low ports (80/443). The
|
||||||
|
Loading…
Reference in New Issue
Block a user