RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1881894 - podman-remote: dial unix ///run/podman/podman.sock: connect: no such file or directory
Summary: podman-remote: dial unix ///run/podman/podman.sock: connect: no such file or ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.3
Assignee: Jindrich Novy
QA Contact: Edward Shen
Gabriela Nečasová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-23 10:39 UTC by Edward Shen
Modified: 2021-05-18 15:33 UTC (History)
9 users (show)

Fixed In Version: podman-3.0
Doc Type: Bug Fix
Doc Text:
.`podman system connection add` automatically set the default connection Previously, the `podman system connection add` command did not automatically set the first connection to be the default connection. As a consequence, you must manually run the `podman system connection default <connection_name>` command to set the default connection. With this update, the `podman system connection add` command works as expected.
Clone Of:
Environment:
Last Closed: 2021-05-18 15:32:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Daniel Walsh 2020-09-23 14:10:22 UTC 
Did you enable the podman.socket in systemd?

# systemctl enable --now podman.socket
Comment 2 Brent Baude 2020-09-23 14:14:40 UTC 
you need to enable a default connection with `podman-remote system connection default root`.  then it will work.
Comment 3 Brent Baude 2020-09-23 14:16:03 UTC 
@jhonce, i thought if there were no connections and you added one, it would automatically become the default?
Comment 4 Daniel Walsh 2020-09-23 15:30:44 UTC 
We should just add this to Release notes for now, and it will be fixed in RHEL 8.3.1
Comment 16 Daniel Walsh 2021-01-28 12:10:38 UTC 
Fixed in podman 3.0
Comment 28 Daniel Walsh 2021-03-18 13:40:11 UTC 
Sure but I don't find any DocText field?
Comment 30 Daniel Walsh 2021-03-22 18:57:53 UTC 
LGTM
Comment 33 errata-xmlrpc 2021-05-18 15:32:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1796
Note You need to log in before you can comment on or make changes to this bug.