linuxserver/docker-syslog-ng

[BUG] No such file ...

Mephisto090 opened this issue · 6 comments

Mephisto090 commented

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Hi,

image

Expected Behavior

That no more errors are displayed and a log is created

Steps To Reproduce

Start vanilla the docker compose

Environment

- OS: Ubuntu 22.04
- How docker service was installed: docker compose

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

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 4.7.1-r1-ls126
Build-date: 2024-09-05T18:56:30+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.
github-actions commented

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

thespad commented

Are there messages and/or messages-kv.log files in the directory you've mounted? Does the user have write access to that location?

Mephisto090 commented

No, the files are not in the mounted folder. docker compose was run with root

thespad commented

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

LinuxServer-CI commented

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.

github-actions commented

This issue is locked due to inactivity