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 1365206 - Cockpit pulls in cockpit-docker by default
Summary: Cockpit pulls in cockpit-docker by default
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.2
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: ---
Assignee: Dominik Perpeet
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1349375
Blocks: 1309887 ovirt-node-ng-platform
TreeView+ depends on / blocked
 
Reported: 2016-08-08 15:35 UTC by Dominik Perpeet
Modified: 2016-08-08 20:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1349375
Environment:
Last Closed: 2016-08-08 20:40:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Dominik Perpeet 2016-08-08 15:37:39 UTC 
We only fixed the dependency on docker from cockpit-shell in 0.113, but the cockpit metapackage still pulls in cockpit-docker.
Comment 2 Dominik Perpeet 2016-08-08 15:42:10 UTC 
The question is, do we want cockpit to pull in docker where available? How will someone who has docker know to install cockpit-docker?
Comment 4 Dominik Perpeet 2016-08-08 20:40:00 UTC 
After some discussion Stef Walter, Fabian Deutsch and I came to the conclusion that it wouldn't be good for now to remove cockpit-docker from the cockpit metapackage. Cockpit is about discoverability, and right now a user would have difficulty finding out about cockpit-docker.

For that reason it is recommended that consumers who aren't happy with the choice of packages required by the metapackage be picky about what they pull in, at least until all affected distributions support Recommends/Suggests nomenclature in their packaging.

Discounting cockpit-docker, a consumer would need to use the following packages to get the equivalent experience:

cockpit-bridge
cockpit-shell
cockpit-ws
cockpit-storaged
cockpit-networkmanager (only non-RHEL)

On RHEL, a few upstream packages are part of the cockpit-shell package:
cockpit-subscriptions, cockpit-sosreport and cockpit-networkmanager

cockpit-ws can of course also be replaced with the cockpit-ws-docker container.

Spec file: https://github.com/cockpit-project/cockpit/blob/ce83dc7103c79a569663e8903e80ca6c1d97ab6c/tools/cockpit.spec#L90
Note You need to log in before you can comment on or make changes to this bug.