Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause:
docker was labeling shared volumes private by default.
Consequence:
Other containers could not use the content
Fix:
Fixed the code to label shared volumes correctly
Result:
Shared volumes now work with SELInux in enforcing mode.
In docker-1.6.2-10.el7.x86_64, all container can start, move to verified
# docker ps
b98dbc7568a1 shipyard/shipyard:latest "/controller" About a minute ago Up About a minute 0.0.0.0:8080->8080/tcp shipyard
cd4b7fd520d0 shipyard/rethinkdb:latest "/usr/bin/rethinkdb 4 minutes ago Up 4 minutes 0.0.0.0:32770->8080/tcp, 0.0.0.0:32768->28015/tcp, 0.0.0.0:32769->29015/tcp shipyard-rethinkdb
b148891c324d shipyard/rethinkdb:latest "/bin/bash -l" 6 minutes ago Up 6 minutes 8080/tcp, 28015/tcp, 29015/tcp shipyard-rethinkdb-data
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://rhn.redhat.com/errata/RHBA-2015-1167.html
Description of problem: shipyard doesn't start with docker 1.6.0. Upgrading the binary from docker 1.6.2 fixed the problem. Version-Release number of selected component (if applicable): docker-1.6.0 How reproducible: static Steps to Reproduce: 1. docker run -it -d --name shipyard-rethinkdb-data \ --entrypoint /bin/bash shipyard/rethinkdb -l 2. docker run -it -P -d --name shipyard-rethinkdb \ --volumes-from shipyard-rethinkdb-data shipyard/rethinkdb 3. docker run -it -p 8080:8080 -d --name shipyard \ --link shipyard-rethinkdb:rethinkdb shipyard/shipyard Actual results: exit code 2 with error FATA0024 Expected results: shipyard container should start Additional info: upstream bug is https://github.com/shipyard/shipyard/issues/554