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
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.
That is not true anymore. https://podman-desktop.io/docs/compose/running-compose
Is that a podman-desktop exclusive feature?
Dont think so. Desktop application relies on podman