Skip to content

[BUG] ALLOW_START, ALLOW_STOP, and ALLOW_RESTARTS #32

@christianha1111

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions