Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1369255 - [RFE] Add ability to mount volumes in Docker
Summary: [RFE] Add ability to mount volumes in Docker
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 20:55 UTC by jcallaha
Modified: 2018-07-17 19:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-17 19:49:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20772 0 None None None 2017-08-28 18:42:27 UTC

Description jcallaha 2016-08-22 20:55:28 UTC
Description of problem:
There currently is no way to specify a volume to be mounted when starting a docker container. This dramatically limits the usefulness of creating containers in Satellite (e.g. configuration files, persistent storage). For example, in order to run goferd in a container, you must mount /dev/log. As it stands there is no current way to do this with Satellite.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a new docker container in UI, specifying a volume to be mounted.
2. Create a new docker container in hammer, specifying a volume to be mounted.

Actual results:
There is no way to specify a volume to be mounted.

Expected results:
You can specify at least one volume to be mounted, and option for multiples would be preferred.

Comment 1 Sebastian Gräßl 2017-08-28 18:42:20 UTC
Created redmine issue http://projects.theforeman.org/issues/20772 from this bug

Comment 2 Bryan Kearney 2018-07-17 19:49:58 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.