Describe the bug
Logs are available from the CLI, but the log folder itself is empty. Would be helpful to have the logs as files.
To Reproduce
- Play a channel in M3UE.
- Verify logs in host CLI: `docker logs <m3u-proxy_container_name>
- Open log folder in persistent volume and verify the folder is empty.
Expected behavior
I expected a daily log file of the m3u-proxy container.
Actual behavior
No log files produced, despite logs available via CLI.
Screenshots
N/A
docker-compose.yml contents
m3u-proxy:
image: sparkison/m3u-proxy:latest
container_name: m3u-proxy
network_mode: "service:gluetun"
volumes:
- $DOCKERDIR/appdata/m3u-proxy/tmp/m3u-proxy-streams:/tmp/m3u-proxy-streams
- $DOCKERDIR/appdata/m3u-proxy/logs:/app/logs
devices:
- /dev/dri:/dev/dri # Intel/AMD GPU support
environment:
- M3U_PROXY_HOST=0.0.0.0
- M3U_PROXY_PORT=8085
- LOG_LEVEL=${LOG_LEVEL:-INFO}
- ROOT_PATH=/m3u-proxy
- LIBVA_DRIVER_NAME=iHD
- CLIENT_TIMEOUT=300
- CLEANUP_INTERVAL=60
- API_TOKEN=REDACTED
restart: unless-stopped
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8085/health?api_token=REDACTED"]
interval: 30s
timeout: 10s
retries: 3
start_period: 10s
Container/Host Logs
cli-log.txt
Additional context
BallerMC reports the same issue.
Describe the bug
Logs are available from the CLI, but the log folder itself is empty. Would be helpful to have the logs as files.
To Reproduce
Expected behavior
I expected a daily log file of the m3u-proxy container.
Actual behavior
No log files produced, despite logs available via CLI.
Screenshots
N/A
docker-compose.yml contents
Container/Host Logs
cli-log.txt
Additional context
BallerMC reports the same issue.