Love their ‘terms of service’ and complete lack of privacy policy (at least for me, the link is not showing any policy). Whoever pays for this nonsense gets what they deserve.

Ah, looks like I should have used journalctl -b | grep stirling-pdf

A couple of reasons - I switched from Pop! OS to OpenSUSE Tumbleweed, and the Docker version in the repository is 24.07 compared to 25.02 (the current version of Docker) with the official Docker site only supporting SLES on s390x, not Tumbleweed on x86_64. The main reason though is that it can run without root which is appealing; apparently I have a lot to learn on setting that up. The glib statements of ‘drop in replacement’ that I"ve seen isn’t quite accurate apparently outside of the commandline options.

I didn’t know enough to try running it interactively - that was a great suggestion and showed many access denied errors trying to access a log file path, so thanks for that suggestion.

Interesting, it runs if I remove the mount points. It’s binding to port 8080, so nothing to do with privileged ports here. I’ll need to look into the subuid and subgid edits - I read the docs for those and understood them to be for multiple users on the same machine running the same container, didn’t realize it was for all users including my own but that makes sense. Thanks for the direction!

Looks like it is the mount points; if I remove those it runs. Going to follow @ubergeek77’s suggestion. (Does tagging with @ work on Lemmy?)

Thanks - this shows exited (1). Running in foreground mode from another suggestion shows the same access denied and file not found error repeatedly - 'Suppressed: java.io.FileNotFoundException: logs/info.log (Permission denied). Looks like I don’t have podman configured correctly, going to work through that.

Thanks, docker.io/frooodle/s-pdf:latest was the only repository that would download it from the options it gave me. I’m working through the other suggestions as well. journalctl isn’t giving me anything when I try grep with stirling, podman or s-pdf. It’s 100% likely I’m not using journalctl properly either.

power

You’re confusing developers with power users here. At my company, the developers can do one thing well, but are far, far from power users with any technology. The amount of times I’ve seen them get stuck at a simple error message without doing more than throwing their hands up thinking they don’t have permissions or something is actually broken, without doing the least bit of troubleshooting is both baffling and frustrating.