[BUG] ALLOW_START, ALLOW_STOP, and ALLOW_RESTARTS

[christianha1111]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

ALLOW_START, ALLOW_STOP, and ALLOW_RESTARTS to work even with POST=0 seems to be broken. I required POST=1 to allow portainer to restart my containers. That was the feature I was looking for that tecnativa/docker-socket-proxy doesn't offer.

Expected Behavior

No response

Steps To Reproduce

.

Environment

- OS:
- How docker service was installed:

Docker creation

docker-socket-startstopdelete:
    image: ghcr.io/linuxserver/socket-proxy
    container_name: docker-socket-startstopdelete
    environment:
      - ALLOW_START=1 #optional
      - ALLOW_STOP=1 #optional
      - ALLOW_RESTARTS=1 #optional
      - AUTH=0 #optional
      - BUILD=0 #optional
      - COMMIT=0 #optional
      - CONFIGS=0 #optional
      - CONTAINERS=1 #optional
      - DISABLE_IPV6=0 #optional
      - DISTRIBUTION=0 #optional
      - EVENTS=1 #optional
      - EXEC=0 #optional
      - IMAGES=1 #optional
      - INFO=1 #optional
      - LOG_LEVEL=info #optional
      - NETWORKS=1 #optional
      - NODES=0 #optional
      - PING=1 #optional
      - PLUGINS=1 #optional
      - POST=0 #optional
      - SECRETS=0 #optional
      - SERVICES=0 #optional
      - SESSION=0 #optional
      - SWARM=0 #optional
      - SYSTEM=1 #optional
      - TASKS=1 #optional
      - VERSION=1 #optional
      - VOLUMES=1 #optional
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    networks:
      - docker-socket-startstopdelete
    restart: unless-stopped

Container logs

nothing special in there.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thespad]

I can't replicate this. With the following permissions set I can stop/restart containers as expected

    environment:
      - ALLOW_START=1
      - ALLOW_STOP=1
      - ALLOW_RESTARTS=1
      - CONTAINERS=1
      - NETWORKS=1
      - IMAGES=1
      - VOLUMES=1
      - POST=0

Can you provide container logs as these should show the individual requests being made for the start/stop/restart requests? e.g.

::ffff:172.22.0.51:37324 [04/May/2025:13:14:33.919] proxy docker/socket 0/0/0/210/210 204 152 - - ---- 3/3/0/0/0 0/0 "POST /v1.41/containers/8ab658a22f86c276e99208e515465ae70318ff713c814ae2033681866a723431/restart HTTP/1.1"

[christianha1111]

You are right. I just tried again and I can't reproduce it neither. It works flawlessly now yet it bugged me for an hour last night. I'm sorry to have wasted your time.

I ended up solving my objective with ngnix in front of it. That also allowed me to do deletion while filtering out create containers which was what I'm really worried about.

Might be a nice addition to socket-proxy. Happy to submit a feature request if that is something doable.