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.

Description of problem:
docker 1.10.x needs libseccomp-static as a build dependency. Could you please provide this in the next update. This would be needed in rhel 7.2.4

Dan, docker rpmbuild does succeed without libseccomp-static if we remove seccomp from DOCKER_BUILDTAGS. Would that be ok or would you prefer we wait for this to be added?

We want to support seccomp, but in order to get testing started, lets do that, but put it in the comments for now.  We need to make sure the docker-latest we ship has seccomp support.  

Only reason we need this is for dockerinit, which thankfully disappears in docker-1.11.

setting this to high priority as we need this to get seccomp enabled RE: Bug 1327679

Can we just build dockerinit without static and then not ship it.

Created attachment 1147774 [details]
If you add this patch I believe dockerinit will compile without libseccomp-static.

(In reply to Daniel Walsh from comment #6)
> Created attachment 1147774 [details]
> If you add this patch I believe dockerinit will compile without
> libseccomp-static.

yup that works. I'm gonna close this.