Hi

The Unix Adm function is part of Manage Services.  I assumed they read the podman Unix setup/configuration documentation and performed whatever was required for normal operations of podman and for non-root operations.  After reading other replies on this issue and looking at /etc on the server I can see they did not.

So, I have requested the OS level changes documented for podman be completed.  Once that is done I will remove the workaround and see if Podman works.

Thanks for the help.  Will get back to you on the results.  I hope to know very soon.

Kent Collins

Office:  817.352.0251 | Enterprise Information Management | Cell: 817.879.7764

Data Solutions Architect/Scientist – Published Author and Conference Speaker

“Death and life are in the power of the tongue: and they that love it shall eat the fruit thereof.”

Prov 18:21

From: Scott McCarty [mailto:smccarty@redhat.com]
Sent: Wednesday, August 18, 2021 9:21 AM
To: Collins, Kent <Robert.Collins@BNSF.com>
Cc: jeremy.valcourt@gmail.com; dwalsh@redhat.com; podman@lists.podman.io
Subject: Re: [Podman] Podman on Redhat

EXTERNAL EMAIL

Kent,

    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 to do.

Best Regards

Scott M 

On Wed, Aug 18, 2021 at 10:16 AM Collins, Kent <Robert.Collins@bnsf.com> wrote:

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 of podman.

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

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 operations.  Stop/start/rm/run/load

Any help to get this working would be appreciated.

==> podman --version

podman version 3.0.2-dev

x    /etc/*ease[1]: NAME="Red Hat Enterprise Linux"                                                                                                 x

x    /etc/*ease[2]: VERSION="8.4 (Ootpa)"                                                                                                           x

x    /etc/*ease[3]: ID="rhel"                                                                                                                       x

x    /etc/*ease[4]: ID_LIKE="fedora"                 

Kent Collins

Office:  817.352.0251 | Enterprise Information Management | Cell: 817.879.7764

Data Solutions Architect/Scientist – Published Author and Conference Speaker

“Death and life are in the power of the tongue: and they that love it shall eat the fruit thereof.”

Prov 18:21

_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io

--

--
18 ways to differentiate open source products from upstream suppliers: https://opensource.com/article/21/2/differentiating-products-upstream-suppliers 
--
Scott McCarty
Product Management - Containers, Red Hat Enterprise Linux & OpenShift
Email: smccarty@redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com