Daniel

These are our varnish4 startup flags, I'm not sure if they're relevant or useful: ``` DAEMON_OPTS="-a :6081 \ -p vcc_allow_inline_c=on \ -p thread_pool_add_delay=2 \ -p thread_pools=2 \ -p thread_pool_min=25 \...

It says on your page (http://www.bobandlush.ch/de/60-ententrockenfutter.html), twice the following: ESI processing not enabled ESI processing not enabled In varnish4 (I'm not sure about varnish3), esi processing must explicitly be enabled...

You could simply chain the commands with `&&`. Though i don't fully disagree, if there is command splitting logic (i saw something like that in the code, just glancing at...

@nikola-jokic i think your link for the spec should not refer to the sha `abc0b678d323b` but to a newer one (or master). The sha referenced might be missleading since it...

We just did the migration to the new runner scale sets. Basically what is important is to have the docker socket available on `/var/run/docker.sock` there are implicit assumptions present which...

Should we update the README/docs to add this improvement? I think the current `dind` spec expansion example is not what people expect (this was at least the case when i...

@ananthu1834 sounds like the init containter gave a non zero exit code. you should be able to get hints as to why in the logs of that startup process

Just to be sure, you're sharing the `/var/run/` directory, not `/var/run/docker.sock` (like in my above example)? I tried sharing only the socket myself but that didn't work for me either,...

We should update that example template I think. It's not yielding the behavior which people expect and therefore is not a good baseline to start customizing one's own environment

I agree, that the in-memory configuration is not for everyone and should not be what should end up in the README I would say that your example, stripped to the...