[BUG] Support for LOG_LEVEL was removed

[texclayton]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The change to nginx removed the support for the LOG_LEVEL environment variable.

Please bring back the changes in bb302b5 since haproxy is again being used.

I found this because docker-socket-proxy is currently exiting with status 0 after days and I have no insight into why and cannot get 'debug' level logs.

Expected Behavior

LOG_LEVEL environment variable should be usable to specify the logging level.

Steps To Reproduce

1. Specify LOG_LEVEL in the environment variables for the docker.
2. Watch the logs.

Environment

- OS:
- How docker service was installed:

Docker creation

I'm using docker compose:

networks:
  socket_proxy:
    name: socket_proxy

services:
  socket-proxy:
    image: lscr.io/linuxserver/socket-proxy:latest
    container_name: socket-proxy
    networks:
      - socket_proxy
    environment:
      - LOG_LEVEL=${LOG_LEVEL:-info} # debug,info,notice,warning,err,crit,alert,emerg
      ...
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    restart: unless-stopped
    read_only: true
    tmpfs:
      - /run

Container logs

The last lines before the service died (not really applicable to the issue at hand, but I'm required to put something here...)

172.20.1.6 - - [08/Apr/2025:09:02:36 +0000] "GET /v1.25/images/containrrr/watchtower:latest/json HTTP/1.1" 200 2087 "-" "Go-http-client/1.1"

172.20.1.8 - - [08/Apr/2025:09:02:36 +0000] "GET /v1.47/containers/json HTTP/1.1" 200 70382 "-" "Go-http-client/1.1"

172.20.1.6 - - [08/Apr/2025:09:02:36 +0000] "GET /v1.25/images/louislam/uptime-kuma:latest/json HTTP/1.1" 200 3816 "-" "Go-http-client/1.1"

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