varnishadm exit code 200
martynas at atomgraph.com
Sat Oct 2 22:23:33 UTC 2021
Actually it does not seem to be the exit code. I tried checking and it
looks like the exit code is 0:
root at dc17c642d39a:/etc/varnish# varnishadm "ban req.url ~ /"
root at dc17c642d39a:/etc/varnish# test $? -eq 0 || echo "Error"
root at dc17c642d39a:/etc/varnish#
So where is that "200" coming from?
On Sun, Oct 3, 2021 at 12:14 AM Martynas Jusevičius
<martynas at atomgraph.com> wrote:
> We recently switched to the varnish:latest container and based an
> unprivileged image on it (entrypoint runs as USER varnish):
> We noticed that our varnishadm commands started failing. More specifically:
> root at dc17c642d39a:/etc/varnish# varnishadm "ban req.url ~ /"
> As I understand it's a 200 exit code, which means varnishadm failed:
> What does 200 mean exactly? I couldn't find any code list.
> My guess is that this has to do with the unprivileged varnish user,
> but I'm not sure what it takes to fix it.
More information about the varnish-misc