We'd be happy to help, but I can't quite discern what you're trying to
do. I've never seen these workarounds that you mention, so I don't know
what they are trying to work around. When you say "simple API service," I
think of a web service, but maybe you are trying to share a Unix socket?
As for su and sudo breaking, I have never seen that happen in RHEL with
Podman. I'd be happy to do a remote session to dig into what you're trying
On Wed, Aug 18, 2021 at 10:16 AM Collins, Kent <Robert.Collins(a)bnsf.com>
So far running Podman ( non-Root ) on Redhat has been a horrible
experience. It seems to take very little to break Podman.
From breaking when using su or sudo to the directory length issue, these
simple normal Unix everyday operations seem to be difficult for development
I am trying to run a very simple API container using Podman as non-root
and at this point I cannot start any containers.
On top of that, workarounds found in searching for solutions also never
For example these two work arounds do not work.
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus
systemd-run --scope --user $SHELL
I will admit I am not a Podman expert. My goal in using Podman over
Docker should not require it. It only needs to perform basic container
Any help to get this working would be appreciated.
==> podman --version
podman version 3.0.2-dev
x /etc/*ease: NAME="Red Hat Enterprise
x /etc/*ease: VERSION="8.4
x /etc/*ease: ID_LIKE="fedora"
Office: 817.352.0251 | Enterprise Information Management | Cell:
Data Solutions Architect/Scientist – Published Author and Conference
“Death and life *are* in the power of the tongue: and they that love it
shall eat the fruit thereof.”
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
18 ways to differentiate open source products from upstream suppliers:
Product Management - Containers, Red Hat Enterprise Linux & OpenShift