RSS Bot Posted July 12 Share Posted July 12 Description Follow-up to #6927 Bind mount /dev into the container Remove previous attempt via MKNOD capability which actually didn't affect the issue GitHub issue reference: #6568 Jira reference number AR-2132 Documentation summary for feature / change The issue has been found in other projects as well, and they end up bind mounting /dev into the container: https://github.com/moby/moby/issues/27886 https://github.com/moby/moby/issues/16160 The issues have a lot of discussion on the various aspects of the problem and solutions. The most accepted one is binding /dev into the container. The MKNOD capability doesn't solve the issue, as it turns out. Testing in #6927 was faulty, as the device is available by the next launch, and the most reliable way to remove it that I've found is to reboot the machine. How Has This Been Tested? Fresh system boot, run ./compile.sh build BOARD=odroidm1 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm PREFER_DOCKER=yes Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article Link to comment Share on other sites More sharing options...
Recommended Posts