Bug 1881894
| Summary: | podman-remote: dial unix ///run/podman/podman.sock: connect: no such file or directory | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Edward Shen <weshen> |
| Component: | podman | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | Edward Shen <weshen> |
| Severity: | medium | Docs Contact: | Gabriela Nečasová <gnecasov> |
| Priority: | unspecified | ||
| Version: | 8.3 | CC: | bbaude, dwalsh, gnecasov, jhonce, jligon, jnovy, lsm5, mheon, tsweeney |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-18 15:32:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Daniel Walsh
2020-09-23 14:10:22 UTC
you need to enable a default connection with `podman-remote system connection default root`. then it will work. @jhonce, i thought if there were no connections and you added one, it would automatically become the default? We should just add this to Release notes for now, and it will be fixed in RHEL 8.3.1 Fixed in podman 3.0 Sure but I don't find any DocText field? LGTM 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 |