collabnix / collabnix/dockerlabs
docs: Capabilities page - Images can store file-based capabilities
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
https://dockerlabs.collabnix.com/advanced/security/capabilities/
These are inaccurate. The limitation was removed with BuildKit / buildx IIRC which has been the default image builder since Docker 23 (released Feb 2023), which can preserve extended file attributes.
I believe the main issue prior was that you'd lose the extended attributes via a COPY but they would otherwise remain intact so long as the image layer was on a file system that supported the file attributes? (I recall an issue with AUFS, which may still be problematic for some NAS systems)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open advanced/security/capabilities/README.md and inspect the statements at lines 37 and 281, along with the linked Capabilities page. Verify the current BuildKit/buildx behavior around file-based capabilities, COPY, extended attributes, and filesystem limitations. Done means the inaccurate limitations are corrected consistently in the README and rendered documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100