-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] No such file ... #28
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Are there messages and/or messages-kv.log files in the directory you've mounted? Does the user have write access to that location? |
No, the files are not in the mounted folder. docker compose was run with root |
No, not which account did you run the container creation with, I'm talking about the account you're running the container application as (1000:1000). |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
Hi,
Expected Behavior
That no more errors are displayed and a log is created
Steps To Reproduce
Start vanilla the docker compose
Environment
CPU architecture
x86-64
Docker creation
services: syslog-ng: image: lscr.io/linuxserver/syslog-ng:latest container_name: Tasmota-Syslog environment: PUID: 1000 PGID: 1000 TZ: Europe/Berlin volumes: - ./config:/config - ./log:/var/log #optional ports: - 514:5514/udp - 601:6601/tcp - 6514:6514/tcp restart: unless-stopped
Container logs
The text was updated successfully, but these errors were encountered: