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: When starting several containers in rapid succession, some of them fail to start.


Version-Release number of selected component (if applicable): docker-1.9.1-14.el7


How reproducible: occasionally


Steps to Reproduce:
1. docker pull busybox
2. for i in `seq 1 100`; do docker run -d busybox sleep 1d; done

Actual results: most containers start ok, but some fail to start with an error like this:

Error response from daemon: Cannot start container 51cf9a82241f081ed9102875dd937906fb68b413618f883a0ab62f9421d51870: [8] System error: write /sys/fs/cgroup/devices/system.slice/docker-51cf9a82241f081ed9102875dd937906fb68b413618f883a0ab62f9421d51870.scope/cgroup.procs: no such device



Expected results: all containers start ok


Additional info:

docker-1.8.2-10 doesn't appear to have this issue. docker-1.9.1-4 on Fedora 23 doesn't appear to have this issue either.

I've done a bit of testing of upstream docker HEAD (commit fff1511c56e35cf5230d05af2282d31d23a31dc0) and so far haven't been able to reproduce.

Bugzilla was giving me errors when I tried to create this bug, and apparently it created 2 copies. I'm closing this one in favor of https://bugzilla.redhat.com/show_bug.cgi?id=1302418.

*** This bug has been marked as a duplicate of bug 1302418 ***