Bug 1693154
| Summary: | Varlink subcommand is missing for podman in rhel-8.0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Joy Pu <ypu> |
| Component: | podman | Assignee: | Brent Baude <bbaude> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | arusso, ddarrah, dornelas, dwalsh, furlongm, jligon, lsm5, mheon, pthomas |
| Target Milestone: | rc | ||
| Target Release: | 8.1 | ||
| 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-11-05 21:01:58 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: | |||
|
Description
Joy Pu
2019-03-27 09:07:54 UTC
We did not remove podman varlink from RHEL. We only removed the Client side. You can still communicate using varlink to the server. Other packages like cockpit-podman and manually calling via varlink still exist. I don't see a reason to remove the service files. On RHEL 8.0, the io.podman service fails to start, due to missing varlink:
# systemctl start io.podman
# systemctl status io.podman
● io.podman.service - Podman Remote API Service
Loaded: loaded (/usr/lib/systemd/system/io.podman.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2019-06-10 18:38:41 EDT; 4s ago
Docs: man:podman-varlink(1)
Process: 10552 ExecStart=/usr/bin/podman varlink unix:/run/podman/io.podman (code=exited, status=125)
Main PID: 10552 (code=exited, status=125)
Jun 10 18:38:40 dev-10-34-0-40 systemd[1]: Started Podman Remote API Service.
Jun 10 18:38:41 dev-10-34-0-40 podman[10552]: Command "varlink" not found.
Jun 10 18:38:41 dev-10-34-0-40 podman[10552]: See `podman --help`.
Jun 10 18:38:41 dev-10-34-0-40 systemd[1]: io.podman.service: Main process exited, code=exited, status=125/n/a
Jun 10 18:38:41 dev-10-34-0-40 systemd[1]: io.podman.service: Failed with result 'exit-code'.
see comment #6 Test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64 and the varlink subcommand is already shows up. So set this to verified. Details # podman varlink -h Run varlink interface Description: Run varlink interface. Podman varlink listens on the specified unix domain socket for incoming connects. Tools speaking varlink protocol can remotely manage pods, containers and images. Usage: podman varlink [flags] [URI] Examples: podman varlink unix:/run/podman/io.podman podman varlink --timeout 5000 unix:/run/podman/io.podman Flags: -t, --timeout int Time until the varlink session expires in milliseconds. Use 0 to disable the timeout (default 1000) 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/RHSA-2019:3403 |