ALLOW_RESTARTS doesn't work

[ThorpeJosh]

If I set the environment variable ALLOW_RESTARTS=1 then permission is still denied for any stop/restart/kill operation due to them all being POST methods (blocked by default).

If I set the environment variable POST=1 then stop/restart/kill operations work even if ALLOW_RESTARTS=0.

Is this a bug or is ALLOW_RESTARTS a depreciated configuration? It is not in the README.md but it is still in the haproxy.cfg.

[JiggsNephron]

Wondering the same here. I have to enable Post entirely even though all I need is restart. I was hoping to be able to be more granular by using ALLOW_RESTARTS=1 without POST=1.

[raetha]

I was looking at this same issue and it appears that the block for POST occurs in the rules before the allow statements for stop, start, and restart. That appears to be creating the situation where POST is still required since that rule is applied first. I believe the three new allow rules just need to be placed above the POST blocking rule and this should work as documented. Unfortunately it needs to be fixed in the repo, or you would need to build your own docker image. It isn't something that can be changed on the fly in the existing container image.

[lordraiden]

Is this still an issue? it's general or applies to an specific container?

Still you can limit to witch container applies

ALLOW_START (containers/id/start)
ALLOW_STOP (containers/id/stop)
ALLOW_RESTARTS (containers/id/stop|restart|kill)

But I don't understand the syntax, how it would be? considering that the container is called traefik-int?

environment:
- ALLOW_RESTARTS=containers/traefik-int/stop|restart|kill)