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 must log in or register to comment.
You need to tell Podman which container repo to use. Contrary to Docker it doesn’t just assume Dockerhub. Try with
docker.io/frooodle/s-pdf:latestIf you run the Podman container via the systemd integration it will have logs like any other service.
Ah, looks like I should have used journalctl -b | grep stirling-pdf
You are giving it the
-dflag.-dmeans “detached.” There are logs, you are just preventing yourself from seeing them.Replace the
-dwith 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/subuidand/etc/subgidto get containers to run:More than likely, this might have something to do with podman being unprivileged, and this wanting to bind to port
80in the container (a privileged port). You may need to specify a--usernsflag to podman.Running in interactive mode will give you the logs you want and will hopefully point you in the right direction.
podman logs [container id]just curious; why would you like to use podman over docker? I have a lot of docker containers running, wondering if I should switch to podman.
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.
interesting! So I should be able to throw my docker-compose yamls directly at Podman and be good to go?
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
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.
What exit code shows when you execute podman ps -a?
Does it run in the foreground? It works for me if I run
podman run -it --rm docker.io/frooodle/s-pdf:latest. Maybe it’s something with the application itself and some data in those mount points?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?)
