2.4.202 not starting (podman)

[wsanders00]

It's been a while since I ran this container, historically it ran fins via podman using a pretty basic run command:

# UISP
podman run -d \
  --name=uisp \
  --restart=unless-stopped \
  -p 8082:80 \
  -p 8444:443 \
  -p 8081:8081 \
  -p 2055:2055/udp \
  -e TZ='America/New_York' \
  -v ~/uisp:/config:Z \
  nico640/docker-unms:latest

However, I don't know which update it stopped working, but diving back into it again, I cannot get it to run. The only difference from before, is I am running via quadlets, but the result is the same as the run command. From the browser, I get "UISP is starting" then "something went wrong."

The logs get long pretty fast, but the repeat ones I am seeing are:

/run/postgresql:5432 - accepting connections
Running docker-entrypoint /home/app/unms/index.js
Sentry release: 
Version: 2.4.202+7dfe74afe8.2025-03-20T18:10:24+01:00
Waiting for database containers
Restoring backups and/or running migrations
/usr/local/bin/docker-entrypoint.sh: line 161: /usr/local/bin/node: Operation not permitted
/usr/local/bin/docker-entrypoint.sh: line 165: /usr/local/bin/node: Operation not permitted
2025-04-06 17:31:24.049 EDT [20397] FATAL:  role "root" does not exist

2025-04-06 17:24:14.799 EDT [667] ERROR:  relation "version" does not exist at character 21
2025-04-06 17:24:14.799 EDT [667] STATEMENT:  SELECT version FROM version WHERE system = 'unms'
{"name":"netflow","hostname":"e962fea62c36","pid":659,"level":50,"msg":"Failed to get DB schema version: relation \"version\" does not exist","time":"2025-04-06T21:24:14.800Z","v":0}

2025-04-06 17:24:20.033 EDT [1011] ERROR:  relation "public.nms_option_view" does not exist at character 29
2025-04-06 17:24:20.033 EDT [1011] STATEMENT:  SELECT "name", "value" FROM public.nms_option_view

Container:

[Unit]
Description=UISP
After=network-online.target

[Container]
AutoUpdate=local
SecurityLabelDisable=true
ContainerName=uisp

Image=docker.io/nico640/docker-unms:latest
Volume=uisp-config.volume:/config:Z

EnvironmentFile=/srv/containers/uisp/.env

PublishPort=8082:80
PublishPort=8444:443
PublishPort=8081:8081
PublishPort=2055:2055/udp

SecurityLabelDisable=true

[Service]
Restart=on-failure

[Install]
WantedBy=multi-user.target default.target

.env

# Vars for UISP

TZ=America/New_York
PUID=1002
PGID=1002

Any troubleshooting tips to try and track down the root cause?

[wsanders00]

Ok, so I found it is an issue with node not being executable. I ran across issue #86, specifically this comment mentioning the use of --privileged.

Adding PodmanArgs=--privileged to the .container allows it to run, however, now I am trying to track down the "why" behind it. Initially, I was trying to run the container rootless (~/.config/containers/systemd). When that didn't work, I moved to running from /usr/share/containers/systemd and it didn't work. Ultimately, keep PUID/GUID as 1002 (non-root user) and running from ~/.config/containers/systemd solved the issue.

The Podman docs mentions:

Rootless containers cannot have more privileges than the account that launched them.

So I would assume this should be a "safe" way of managing it. I would like to know if anyone has any additional input, though.