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!
Comment on Podman - container exits without logs
ubergeek77@lemmy.ubergeek77.chat 9 months ago
You are giving it the -d flag. -d means “detached.” There are logs, you are just preventing yourself from seeing them.
Replace the -d with an -i (for interactive) and try again.
More than likely, this might have something to do with podman being unprivileged, and this wanting to bind to port 80 in the container (a privileged port).
Running in interactive mode will give you the logs you want and will hopefully point you in the right direction.
bravemonkey@lemmy.ca 9 months ago
bravemonkey@lemmy.ca 9 months ago
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.