1. I tried to run varnish_reload_vcl, but I got connection failed.

2. I changed VARNISHD_PARAMS to -p default_grace=3600 -T 127.0.0.1:6082.

3. Now, when I run varnish_reload_vcl the script can connect, but it fails to authenticate:

   

The secret file is there, so the path is correct. What else could be wrong? What should I try or debug?

Thanks!

Hello,
I'm trying to use syslog in my vcl file but that doesn't work.
I can't find the /var/log/syslog file.
How can I make it works please?

vcl 4.0;
import std;
sub vcl_recv {
    if (req.method != "GET" && req.method != "HEAD") {
        std.syslog(180, "BAN " + client.ip + " METHOD " +req.method);
        return (pass);
   }
}

When running from docker-compose, I get the following:

bind(): Cannot assign requested address
varnish_dydra_1  | child (14) Started
varnish_dydra_1  | Child (14) said Child starts

Any idea what the problem with bind() is?

Hello there
Please kindly add a tag in Docker Hub https://hub.docker.com/r/million12/varnish/tags/
Thanks a lot

We are running this Docker Image on a Plesk environment with a custom Magento 2 VCL mapped for starting the image. Everything works well except for ESI includes. A particular case is the menu of a website is not available with Varnish on and a tag like the one below appears instead of the menu

<esi:include src="http://www.domain.com/page_cache/block/esi/blocks/..."></esi:include>

The problem seems to be in the DAEMON_OPTS section of the Image as we discussed with some developers and they suggested we add this in DAEMON_OPTS section.

    -p feature=+esi_ignore_other_elements \
    -p feature=+esi_disable_xml_check \
    -p feature=+esi_ignore_https \
    -p http_resp_hdr_len=16k \
    -p http_resp_size=64k \
    -p workspace_backend=64k \

We tried to add DAEMON_OPTS as a parameter for Docker but it is not working

We also searched for the option to enable them directly in the Docker Image config files and we found this option in 2 locations

Location 1
./etc/varnish/varnish.params

For this we added this line

DAEMON_OPTS="-p feature=+esi_ignore_other_elements -p feature=+esi_disable_xml_check -p feature=+esi_ignore_https -p http_resp_hdr_len=16k -p http_resp_size=64k -p workspace_backend=64k"

Location 2

./usr/lib/systemd/system/varnish.service

For this the config we tried to include the options directly in the ExecStart lines like so

Original config

ExecStart=/usr/sbin/varnishd \
        -P /var/run/varnish.pid \
        -f $VARNISH_VCL_CONF \
        -a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} \
        -T ${VARNISH_ADMIN_LISTEN_ADDRESS}:${VARNISH_ADMIN_LISTEN_PORT} \
        -S $VARNISH_SECRET_FILE \
        -u $VARNISH_USER -g $VARNISH_GROUP \
        -s $VARNISH_STORAGE \
        $DAEMON_OPTS

New Config

ExecStart=/usr/sbin/varnishd \
        -P /var/run/varnish.pid \
        -f $VARNISH_VCL_CONF \
        -a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} \
        -T ${VARNISH_ADMIN_LISTEN_ADDRESS}:${VARNISH_ADMIN_LISTEN_PORT} \
        -S $VARNISH_SECRET_FILE \
        -u $VARNISH_USER -g $VARNISH_GROUP \
        -s $VARNISH_STORAGE \
    -p feature=+esi_ignore_other_elements \
    -p feature=+esi_disable_xml_check \
    -p feature=+esi_ignore_https \
    -p http_resp_hdr_len=16k \
    -p http_resp_size=64k \
    -p workspace_backend=64k \
        $DAEMON_OPTS

Basically $DAEMON_OPTS should have included the options from the previous file yet none of the options are working.

The VCL contains the proper esi tag like so

sub vcl_backend_response {

    set beresp.grace = 3d;

    if (beresp.http.content-type ~ "text") {
       **set beresp.do_esi = true;**
    }

If you have multiple containers for the backend service docker sends back multiple IPs for the linked hostname. Will this image only work with a backend service with a single container?

The tests should also cover passing commands like these described in #1.