Container Still Will Not Deploy After Many Modifications

[Com177]

What installation are you running?

Production (netalertx) 📦

Did I research?

• I have searched the docs https://docs.netalertx.com/
• I have searched the existing open and closed issues
• I confirm my SCAN_SUBNETS is configured and tested as per https://docs.netalertx.com/SUBNETS

The issue occurs in the following browsers. Select at least 2.

• Firefox
• Chrome
• Other (unsupported) - PRs welcome
• N/A - This is an issue with the backend

What I want to do

I have tried to deploy the docker_compose.yml from: install > docker > docker-compose .yml with minor modifications in both this and in a heavily modified form and neither will deploy. It looks like the volumes are not being created. I have a current instance of netalertx (legacy version) running where I want to run this newer version. The legacy container is running in a Docker-Portainer LXC running in Proxmox.

Relevant settings you changed

I had to make some changes to allow "side-by-side" deployment with an existing old instance of netalertx that is currently running. Modification that had to be made to both are:
container_name: netalertx2 (from netalertx)
PUID: ${NETALERTX_UID:-10211} (Port changed from 20211 to 10211)
PGID: ${NETALERTX_GID:-10211} (Port changed from 20211 to 10211)
GRAPHQL_PORT: ${GRAPHQL_PORT:-10212} (Port changed from 20212 to 10212)

I methodically removed parts to the original compose file to see if I could get it to deploy. Changes made to the more simplified compose file include:
REMOVED:
sysctls:
net.ipv4.conf.all.arp_ignore: 1
net.ipv4.conf.all.arp_announce: 2
REMOVED:
tmpfs:
- "/tmp:mode=1777,rw,noexec,nosuid,nodev,async,noatime,nodiratime"

REMOVED:
volumes:
netalertx_data:
AND
volumes:
- type: volume
source: netalertx_data
target: /data
read_only: false
- type: bind
source: /etc/localtime
target: /etc/localtime
read_only: true

AND THEN REPLACED IT WITH
volumes:
- netalertx_config:/data/config:rw #short-form volume (no /path is a short volume)
- netalertx_db:/data/db:rw

THE ERROR MESSAGE IS ALWAYS THE SAME OR SIMILAR

docker-compose.yml

# This YML only contains the necessary modifications. (The heavily modified (simpler) YML is below this one.

services:
  netalertx:
    network_mode: host   # Use host networking for ARP scanning and other services
    image: ghcr.io/netalertx/netalertx:latest
    container_name: netalertx2
    read_only: true

    cap_drop:
      - ALL
    cap_add:
      - NET_ADMIN
      - NET_RAW
      - NET_BIND_SERVICE
      - CHOWN
      - SETUID
      - SETGID

      sysctls:
      net.ipv4.conf.all.arp_ignore: 1
      net.ipv4.conf.all.arp_announce: 2

      volumes:
      - type: volume
        source: netalertx_data
        target: /data
        read_only: false
      - type: bind
        source: /etc/localtime
        target: /etc/localtime
        read_only: true

        tmpfs:
      - "/tmp:mode=1777,rw,noexec,nosuid,nodev,async,noatime,nodiratime"

      environment:
      PUID: ${NETALERTX_UID:-10211}
      PGID: ${NETALERTX_GID:-10211}
      LISTEN_ADDR: ${LISTEN_ADDR:-0.0.0.0}
      PORT: ${PORT:-20211}
      GRAPHQL_PORT: ${GRAPHQL_PORT:-10212}
    mem_limit: 2048m
    mem_reservation: 1024m
    cpu_shares: 512
    pids_limit: 512
    logging:
      options:
        max-size: "10m"
        max-file: "3"
    restart: unless-stopped

volumes:
  netalertx_data:


# Below is the heavily modified (simpler) YML

services:
  netalertx:
    network_mode: host   # Use host networking for ARP scanning and other services
    image: ghcr.io/netalertx/netalertx:latest
    container_name: netalertx2
    read_only: true

    cap_drop:
      - ALL
    cap_add:
      - NET_ADMIN
      - NET_RAW
      - NET_BIND_SERVICE
      - CHOWN
      - SETUID
      - SETGID

    sysctls:
      net.ipv4.conf.all.arp_ignore: 1
      net.ipv4.conf.all.arp_announce: 2

    volumes:
      - netalertx_config:/data/config:rw #short-form volume (no /path is a short volume)
      - netalertx_db:/data/db:rw

    tmpfs:
      - "/tmp:mode=1777,rw,noexec,nosuid,nodev,async,noatime,nodiratime"

    environment:
      PUID: ${NETALERTX_UID:-10211}
      PGID: ${NETALERTX_GID:-10211}
      LISTEN_ADDR: ${LISTEN_ADDR:-0.0.0.0}
      PORT: ${PORT:-10211}
      GRAPHQL_PORT: ${GRAPHQL_PORT:-10212}
    mem_limit: 2048m
    mem_reservation: 1024m
    cpu_shares: 512
    pids_limit: 512
    logging:
      options:
        max-size: "10m"
        max-file: "3"

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.

[jokob-sk]

Thanks for the detailed information. I think there are a couple of issues in the compose examples that are preventing us from isolating the actual deployment problem.

First, the two-volume layout itself is valid. NetAlertX supports mounting /data/config and /data/db separately, although the current documentation recommends the single /data volume for new installations.

However, your simplified compose is missing the top-level volume definitions. If you use:

volumes:
  - netalertx_config:/data/config:rw
  - netalertx_db:/data/db:rw

you also need:

volumes:
  netalertx_config:
  netalertx_db:

at the bottom of the compose file.

There is also an indentation problem in the first compose example. sysctls, volumes, tmpfs and environment need to be at the same indentation level as cap_drop / cap_add. As posted, they appear nested under cap_add, so that file is not a valid representation of the intended Compose configuration.

Your change of PORT from 20211 to 10211 is fine for the side-by-side setup you described, since the existing instance is already using 20211. The important thing is that GRAPHQL_PORT and the web port are both unique.

I would therefore first try the following minimal configuration:

services:
  netalertx:
    network_mode: host
    image: ghcr.io/netalertx/netalertx:latest
    container_name: netalertx2
    read_only: true

    cap_drop:
      - ALL
    cap_add:
      - NET_ADMIN
      - NET_RAW
      - NET_BIND_SERVICE
      - CHOWN
      - SETUID
      - SETGID

    volumes:
      - netalertx_config:/data/config:rw
      - netalertx_db:/data/db:rw
      - /etc/localtime:/etc/localtime:ro

    tmpfs:
      - "/tmp:mode=1777,rw,noexec,nosuid,nodev,async,noatime,nodiratime"

    environment:
      PUID: ${NETALERTX_UID:-10211}
      PGID: ${NETALERTX_GID:-10211}
      LISTEN_ADDR: ${LISTEN_ADDR:-0.0.0.0}
      PORT: ${PORT:-10211}
      GRAPHQL_PORT: ${GRAPHQL_PORT:-10212}

    mem_limit: 2048m
    mem_reservation: 1024m
    cpu_shares: 512
    pids_limit: 512

    logging:
      options:
        max-size: "10m"
        max-file: "3"

    restart: unless-stopped

volumes:
  netalertx_config:
  netalertx_db:

The current official configuration also mounts /etc/localtime and /tmp, and uses a single /data volume by default. ([GitHub]1)

Most importantly, though, the issue currently doesn't contain the actual Docker/Portainer error — only "No response" for app.log. Could you please provide the exact error shown by Portainer/Docker when the container deployment fails, preferably from:

docker compose config
docker compose up

or the equivalent Portainer deployment log?

docker compose config is particularly useful here because it will immediately tell us whether this is a Compose/YAML/volume-definition problem before NetAlertX even starts.

Once we have that error, we should be able to distinguish between a Compose configuration problem and a NetAlertX container startup problem.

This is also consistent with the current project docs: the official baseline uses /data as one persistent volume, explicitly says /data/config and /data/db live inside it, and documents the split-volume layout as supported for backward compatibility. ([GitHub]1)

I am also including a minimal example which I am currently running too:

services:
  netalertx_fresh:
    container_name: netalertx_fresh
    image: ghcr.io/netalertx/netalertx
    network_mode: "host"
    privileged: true
    restart: always
    volumes:
      # these are rw enabled paths on my NAS
      - /volume2/docker_appdata/netalertx_fresh/db:/data/db
      - /volume2/docker_appdata/netalertx_fresh/config:/data/config
    environment:
      - PUID=0
      - GUID=100
      - PORT=22222
    tmpfs: 
      # /tmp is required by php for session save this should be reworked to /services/run/tmp
      - "/tmp:uid=20211,gid=20211,mode=1700,rw,noexec,nosuid,nodev,async,noatime,nodiratime"