pangolin-cli ignoring env variable for socket path

[baldemar-wuda]

Describe the Bug

The Pangolin CLI does not respect the SOCKET_PATH environment variable. Even when the variable is explicitly set, the CLI still attempts to connect using the default socket path.

services:
pangolin-cli:
image: fosrl/pangolin-cli
container_name: pangolin-cli
restart: unless-stopped
network_mode: host
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
environment:
- PANGOLIN_ENDPOINT=https://test.example
- INTERFACE="cli-custom1"
- SOCKET_PATH="/var/run/custom1.sock"
- CLIENT_ID=xxx
- CLIENT_SECRET=xxx

2026-03-07 16:56:45.939731+00:00INFO: 2026/03/07 16:56:45 Starting HTTP server on socket /var/run/olm.sock

This behavior appears to be specific to the Pangolin CLI.
When using the container image fosrl/olm, the SOCKET_PATH environment variable is respected and the service correctly uses the custom socket path.

Environment

• Pangolin CLI Version: 0.5.1

To Reproduce

1. Set the SOCKET_PATH environment variable
2. Start the Pangolin CLI.
3. Observe that the CLI still attempts to connect to the default socket path instead of the one defined in SOCKET_PATH.

Expected Behavior

The CLI should use the socket path provided via the SOCKET_PATH environment variable.

[github-actions]

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

[github-actions]

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.