Selfhosted

40006 readers

623 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Podman - container exits without logs (lemmy.ca)

submitted 9 months ago* (last edited 9 months ago) by bravemonkey@lemmy.ca to c/selfhosted@lemmy.world

19 comments fedilink hide all child comments

I'm new to Podman and so far have been completely frustrated by it.
I don't know if the issue is with the container or Podman since there are just no logs.

I'm trying to run Stirling-PDF, using this command:

podman run -d
-p 8080:8080
-v /location/of/trainingData:/usr/share/tesseract-ocr/5/tessdata
-v /location/of/extraConfigs:/configs
-v /location/of/logs:/logs
-e DOCKER_ENABLE_SECURITY=false
--name stirling-pdf
frooodle/s-pdf:latest

With Docker, I have no issue running the this container. Under Podman the container immediately exits without logs - podman logs stirling-pdf shows nothing.

The same thing happens running the same command with sudo or without sudo but using --rootful. I've also tried removing '-e DOCKER_ENABLE_SECURITY=false ' since it's very Docker specific.

I can run podman run -dt --name webserver -p 8081:80 quay.io/libpod/banner with no issues, so is this something incompatible with the container?

I feel like I'm missing something obvious - like where are the logs?

I'm running on OpenSUSE-Tumbleweed, Podman version 4.9.0

you are viewing a single comment's thread
view the rest of the comments

[–] ubergeek77@lemmy.ubergeek77.chat 4 points 9 months ago* (last edited 9 months ago) (2 children)

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.

Have you completed the podman rootless setup in order to be able to use it? You may need to edit /etc/subuid and /etc/subgid to get containers to run:

https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration

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). You may need to specify a --userns flag to podman.

Running in interactive mode will give you the logs you want and will hopefully point you in the right direction.

[–] bravemonkey@lemmy.ca 1 points 9 months ago

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!

[–] bravemonkey@lemmy.ca 1 points 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.