• Geoff Simmons's avatar
    Set the GID for varnish in the klarlack container to agree with haproxy. · ebd048b9
    Geoff Simmons authored
    For the Unix domain socket over which haproxy and varnish communicate,
    we have chmod 660 and chgrp varnish. haproxy belongs to group varnish
    and thus has write permissions on the socket, which is required in
    Linux to be able to connect.
    
    For that, both containers must have the same group name and GID.
    We've been using 998, since that results from the RPM install for
    Varnish from the official packagecloud repos.
    ebd048b9
Name
Last commit
Last update
..
Dockerfile.controller Loading commit data...
Dockerfile.haproxy Loading commit data...
Dockerfile.klarlack Loading commit data...
Dockerfile.varnish Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
bogo_backend.vcl Loading commit data...
boot.vcl Loading commit data...
buster-backports.list Loading commit data...
haproxy.cfg Loading commit data...
haproxy_exec.sh Loading commit data...
notavailable.vcl Loading commit data...
ready.vcl Loading commit data...
start.cli Loading commit data...
uplex_varnish.repo Loading commit data...
varnishcache_varnish63.repo Loading commit data...
varnishd_exec.sh Loading commit data...