<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 12/14/21 13:04, Srinadh Penugonda
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1016692101.2736601.1639505065308@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="ydp22a39bf5yahoo-style-wrap" style="font-family:
lucida console, sans-serif; font-size: 16px;">
<div>
<div dir="ltr" data-setdir="false">Yes, I did add the mount
point for .mk file of the container. </div>
<div dir="ltr" data-setdir="false">
<div>
<div dir="ltr" data-setdir="false">My bad, missed
mentioning it my previous email.</div>
<div><br style="color: rgb(0, 0, 0); font-family: lucida
console, sans-serif; font-size: 16px;">
</div>
</div>
</div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div dir="ltr" data-setdir="false">It wasnt there before but
even after adding the mount point, it didnt make any
difference in the error that see. </div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div><br>
</div>
<div dir="ltr" data-setdir="false">
<div>
<div>root@sonic:/var/run# ls -F</div>
<div>dbus/ frr/ frrcfgd_client_conn_completed lock/
redis/ redis-chassis/ supervisord.pid
supervisor.sock= utmp</div>
</div>
<div><br>
</div>
</div>
<div dir="ltr" data-setdir="false">
<div>
<div>root@sonic:/var/run/dbus# ls -al</div>
<div>total 4</div>
<div>drwxr-xr-x 2 root root 80 Dec 9 19:02 .</div>
<div>drwxr-xr-x 1 root root 4096 Dec 9 19:03 ..</div>
<div>srwxrw-rw- 1 root root 0 Dec 9 19:02
histmem.socket</div>
<div>srw-rw-rw- 1 root root 0 Dec 9 19:02
system_bus_socket</div>
<div>root@sonic:/var/run/dbus# </div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Is it being blocked by SELinux. SELinux would definitely not allow
this access in a Podman container.<br>
<blockquote type="cite"
cite="mid:1016692101.2736601.1639505065308@mail.yahoo.com">
<div class="ydp22a39bf5yahoo-style-wrap" style="font-family:
lucida console, sans-serif; font-size: 16px;">
<div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div><br>
</div>
<div class="ydp22a39bf5signature">
<div style="font-family:sans-serif;font-size:16px;">
<div style="font-family:sans-serif;font-size:16px;"
dir="ltr"><span><span style="color:rgb(0, 0,
0);font-family:sans-serif;font-size:16px;">~~
Thanks, Srinadh</span></span><br>
</div>
<div style="font-family:sans-serif;font-size:16px;"
dir="ltr"><span><span style="color:rgb(0, 0,
0);font-family:sans-serif;font-size:16px;"><br>
</span></span></div>
<div style="font-family:sans-serif;font-size:16px;"><br>
</div>
</div>
</div>
</div>
<div><br>
</div>
</div>
<div id="ydp33708d9eyahoo_quoted_0376164327"
class="ydp33708d9eyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial,
sans-serif;font-size:13px;color:#26282a;">
<div> On Tuesday, December 14, 2021, 04:08:48 AM PST, Thiago
Macieira <a class="moz-txt-link-rfc2396E" href="mailto:thiago@kde.org"><thiago@kde.org></a> wrote: </div>
<div><br>
</div>
<div><br>
</div>
<div>
<div dir="ltr">On Sunday, 12 December 2021 00:32:13 -03
Srinadh Penugonda wrote:<br clear="none">
> When these processes trying to use dbus, they are not
able to get the dbus<br clear="none">
> conn 40 static DBus::Connection conn =<br
clear="none">
> DBus::Connection::SystemBus();<br clear="none">
<br clear="none">
DId you bind-mount the system bus socket into the
identical path inside the
<div class="ydp33708d9eyqt1229088131"
id="ydp33708d9eyqtfd84874"><br clear="none">
container?</div>
<br clear="none">
<br clear="none">
-- <br clear="none">
Thiago Macieira - thiago (AT) macieira.info - thiago (AT)
kde.org<br clear="none">
Software Architect - Intel DPG Cloud Engineering
<div class="ydp33708d9eyqt1229088131"
id="ydp33708d9eyqtfd26251"><br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
</div>
</div>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>