Bug 1564821 - When doing a CRI-O based install there is no crictl command
Summary: When doing a CRI-O based install there is no crictl command
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-08 02:58 UTC by Scott McCarty
Modified: 2018-04-27 21:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-27 21:32:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Scott McCarty 2018-04-08 02:58:37 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
100%


Steps to Reproduce:
1. yum install cri-o
2. rpm -ql cri-o: https://pastebin.com/hg4J2PSZ
3. No crictl command, so you can't verify containers are running on a node, you have to trust that they are running in CRI-O, by doing a "docker ps" and verifying that nothing is running in docker: BAD.

Actual results:
No command to verify containers running

Expected results:
Would be really nice to have similar functionality to docker


Additional info:
Comment 1 Scott McCarty 2018-04-08 02:59:45 UTC 
Also, I tried building crictl from scratch/upstream code and it fails to connect to the CRI-O/CRI that is installed. It appears to be a version mismatch, but I haven't had a chance to troubleshoot it further yet...
Comment 2 Derek Carr 2018-04-27 21:32:50 UTC 
crctl is not yet GA upstream.  we plan to target delivery of it in 3.11.
Note You need to log in before you can comment on or make changes to this bug.