this post was submitted on 02 Feb 2024
15 points (94.1% liked)

Selfhosted

39937 readers
371 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
15
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
[–] vojel@discuss.tchncs.de 5 points 9 months ago (1 children)

No daemon needed, better security because of rootless approach, but well docker also runs rootless nowadays. Podman came up from frustration from Red Hat over docker, that’s why they developed their own thing. Afaik it is nearly full compatible and can be used as a drop in replacement for docker.

[–] faethon@lemmy.world 1 points 9 months ago (1 children)

interesting! So I should be able to throw my docker-compose yamls directly at Podman and be good to go?

[–] poVoq@slrpnk.net 2 points 9 months ago (1 children)

No, docker-compose is where Podman differs. There are some 3rd party attempts to make it compatible via podman-compose, but most people agree that the Systemd integration of Podman is better anyways and if you really need advanced orchestration then you can use K8 helmcharts with Podman.

[–] vojel@discuss.tchncs.de 2 points 9 months ago (1 children)
[–] poVoq@slrpnk.net 1 points 9 months ago (1 children)

Is that a podman-desktop exclusive feature?

[–] vojel@discuss.tchncs.de 1 points 9 months ago

Dont think so. Desktop application relies on podman