Skip to content
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

Bind mounts end up owned by systemd-resolve #656

Closed
2 tasks done
tomkessler opened this issue Apr 28, 2024 · 3 comments
Closed
2 tasks done

Bind mounts end up owned by systemd-resolve #656

tomkessler opened this issue Apr 28, 2024 · 3 comments
Labels
bug 🐛 Something isn't working Waiting for reply⏳ Waiting for the original poster to respond, or discussion in progress.

Comments

@tomkessler
Copy link

Is there an existing issue for this?

Current Behavior

I'm just getting started with NetAlertX. I've used the basic docker compose from the docs. Strangely, the bind mounted folders are getting owned by "systemd-resolve" (UID=101 on my Ubuntu 20.04 system) when I start the container. That doesn't seem right. When I exec into the container, it seems to be running as root (UID=0).

image

Expected Behavior

I'd expect the folders to be owned by root.

Steps To Reproduce

No response

app.conf

No response

docker-compose.yml

version: "3"
services:
  netalertx:
    container_name: netalertx
    image: jokobsk/netalertx:latest
    environment:
      - TZ=${TZ}
    restart: unless-stopped
    volumes:
      - ./netalertx/db:/app/db
      - ./netalertx/config:/app/config
      - ./netalertx/etc/resolv.conf:/etc/resolv.conf
      # (optional) useful for debugging if you have issues setting up the container
      - ./netalertx/logs:/app/front/log
    network_mode: host

What branch are you running?

Production

app.log

No response

Debug enabled

  • I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.
@tomkessler tomkessler added the bug 🐛 Something isn't working label Apr 28, 2024
@vladaurosh
Copy link
Contributor

Those files are owned by nginx:www-data inside the container, as web server is nginx. id of that user is 101 and group id is 82.

@jokob-sk jokob-sk added the Waiting for reply⏳ Waiting for the original poster to respond, or discussion in progress. label Apr 30, 2024
@jokob-sk
Copy link
Owner

probably duplicate: #652

@jokob-sk
Copy link
Owner

jokob-sk commented May 5, 2024

closing as duplicate

@jokob-sk jokob-sk closed this as completed May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working Waiting for reply⏳ Waiting for the original poster to respond, or discussion in progress.
Projects
None yet
Development

No branches or pull requests

3 participants