Bug 1657303
Summary: | RHEL 7.6.1 varlink is missing in podman and therefore podman systemd service doesn't start | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Christian Stark <cstark> |
Component: | podman | Assignee: | Frantisek Kluknavsky <fkluknav> |
Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7.6 | CC: | dornelas, dwalsh, fkluknav, jligon, lsm5, mheon, umohnani, ypu |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-31 19:21:18 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1186913, 1636853 |
Description
Christian Stark
2018-12-07 16:01:11 UTC
can you report podman info? The varlink API is not build into the RHEL7 podman versions because of a lack of python3 and the varlink packages themselves. The error message you see is actually coming from podman and indicating that the varlink subcommand does not exist. [cloud-user@baude ~]$ sudo podman varlink Command "varlink" not found. See `podman --help`. Because there is no varlink support, the following files should be removed from the RHEL7 package. [cloud-user@baude ~]$ rpm -ql podman | grep systemd /usr/lib/systemd/system/io.podman.service /usr/lib/systemd/system/io.podman.socket @Frantisek, I'm going to re-assign this bug to you because the solution is to remove those systemd files from the package itself on RHEL7 Check with podman-0.12.1.2-2.git9551f6b.el7.x86_64 and the related files are all removed. So set this to verified. 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, 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/RHBA-2019:0241 |